Download the PHP package spora-ai/spora-plugin-memories-frontend without Composer
On this page you can find all versions of the php package spora-ai/spora-plugin-memories-frontend. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download spora-ai/spora-plugin-memories-frontend
More information about spora-ai/spora-plugin-memories-frontend
Files in spora-ai/spora-plugin-memories-frontend
Package spora-plugin-memories-frontend
Short Description Pre-built Vue SPA for the Spora memories admin panel. Delivered as type `spora-plugin-frontend`; the host SPA lazy-loads it via /plugins/spora-plugin-memories-frontend/main.js.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package spora-plugin-memories-frontend
spora-plugin-memories-frontend
Pre-built Vue SPA for the Spora Memories admin panel. Delivered as a Composer package of type spora-plugin-frontend; spora-installer's SporaPluginFrontendInstaller copies this repo's frontend/ directory into public/plugins/spora-plugin-memories-frontend/ so the host SPA can lazy-load it via /plugins/spora-plugin-memories-frontend/main.js.
Why a separate repo from the PHP plugin?
- The Vue bundle has its own release cadence (visual fixes don't need a PHP tag).
- Backend-only operators can
composer require spora-ai/spora-plugin-memorieswithout pulling in npm-buildable assets. - The bundle is independently testable in isolation (Vitest + the smoke script).
What it surfaces
A sidebar-and-detail admin panel (/apps/memories) per user (global memories) and per agent (agent-scoped memories). The plugin's UI mirrors spora-frontend/src/apps/memories/ (which it replaces):
- Scope bar —
PrincipalChipRowtoggles between the caller's user-principal and any group-principals they're a member of. Memory reads and writes are scoped to the active principal (?principal_id=N). - Mode row — segmented
Global/Agent: <name>control. Selecting the agent pill in global mode routes to the first visible agent; in agent mode it opens a dropdown for fast switching. - Documents panel (sidebar) — type-filter chips (
All/Plans/Docs/Examples/Context) live next to the list they filter. Drag-to-reorder persists via PATCH/memories/reorder(global) or PATCH/agents/:id/memories/reorder(agent). - Memory editor — Markdown body via
md-editor-v3(externalised; shared with the host SPA). Edit-only by default (:preview="false"); the toolbar's preview button toggles between edit, split, and preview modes.Attach mediaopens the host'sopenMediaPickerand insertsat end-of-content. Markdown is sanitised via DOMPurify before preview render. - Routing — both
/(global-memories) and/agents/:id(agent-memories/:id) resolve to the same component; mode is derived fromroute.name, active agent fromroute.params.id, and the active memory from?memory=<id>or?create=1.
Document types
Every memory is tagged with a type from the set plan | documentation | examples | context (mandatory on save/get/replace). The Documents panel exposes per-type filter chips; the list endpoints honour ?type= for the same filter.
Build
The build output (main.js + style.css) is committed to this repo. Operators get the new bundle on the next composer update.
Dev mode (plugin author)
The host SPA's vite.config.ts proxies /plugins/spora-plugin-memories-frontend to :5175 so editing src/* updates the panel without rebuilding the host. The dev sandbox uses an in-memory mock API (src/dev-mock.ts) so it renders without the PHP backend — set SPORA_PLUGIN_DEV_PORTS=memories:5175 on the host for the cross-port proxy.
Mount contract
The IIFE bundle installs window.SporaAppMemories (the PascalCase of the slug) with two methods:
mount(target: HTMLElement, hostContext)— create the app, install local Pinia + local router (createMemoryHistory), mount into the host's slot.unmount(target: HTMLElement)— tear down.
The host's apps/registry.ts reads both. The bundle names must stay aligned with memories → SporaAppMemories (see vite.config.ts → build.lib.name).
Plugin-local router
The plugin installs its own vue-router instance with createMemoryHistory() — sidebar and ?create=1 / ?memory=N navigation lives entirely in JS state. The host SPA owns the browser address bar; deep-link routes inside the memories bundle won't change the URL by default. Operators sharing a specific memory view will see only /apps/memories in their address bar.
If you need a future deep-link feature, src/lib/route-detection.ts already parses /apps/memories/agents/:id(/:memoryId)? and returns a typed PluginRouteMatch.
Backend compatibility
The bundle expects a Spora host with the memories plugin installed (spora-ai/spora-plugin-memories >= 0.1.0). The plugin's PHP side provides the /memories and /agents/:id/memories endpoints the bundle calls via hostContext.api.
License
MIT — see LICENSE.
