Package Catalogue
Strutvane’s core is small on purpose. Everything else (a log viewer, billing, search, charts) is a package: a separate npm package that adds one feature to your app and installs itself completely with one command. There will be more than 100 of them over time, so everything that deals with “the list of packages” is driven by data, not by code that names each package.
The smallest example
Section titled “The smallest example”Add a package to an app you already have:
node strut install:log-viewerWhat it will do (something like this; the exact wording isn’t final):
✔ Added @strutvane/log-viewer with npm ✔ Registered its provider in bootstrap/providers.ts ✔ Added its sidebar entry (Logs)
Next: open http://localhost:3000/_strutvane/logsWith Docker, type the same command on your computer: like every node strut command, it runs inside the app container. See Docker.
Three ways in, one installer
Section titled “Three ways in, one installer”Every way of adding a package runs the same installer protocol (the fixed steps every package follows to install itself), so the result is identical whichever you use:
| Way | When you’d use it |
|---|---|
| Installer question 22, “Extra features” | While creating the app with npm create strutvane@latest |
node strut install:<name> |
You know the package you want |
node strut add |
You want to browse or search the catalogue |
Install order never changes the result: installing billing before search gives the same app as search before billing.
What install:<name> does
Section titled “What install:<name> does”- Adds the package with npm.
- Asks the package’s own follow-up questions, if it has any (billing asks “Stripe or Paddle?”).
- Writes its config file (
config/<name>.ts) and adds its.envkeys, with secrets generated into.envonly, never into.env.example. - Copies its migrations into
database/migrations/, where they become ordinary migrations of your app. - Registers its provider in
bootstrap/providers.ts, which adds its routes, commands, screens and sidebar entries.
Choosing packages while you create the app
Section titled “Choosing packages while you create the app”Question 22 never shows a flat list of 100+ packages. It shows a short popular list, grouped, then offers to search the rest:
? Extra features? (popular first; space to toggle, enter to confirm) Operations log viewer (selected), queue dashboard, inspector, health Data charts and dashboards, search, import/export, API explorer Back office activity log, settings, media library, PDF, privacy, backups Integrations feature flags, webhooks, GraphQL, realtime, notification channels Money billing, invoicing AI AI SDK, MCP server? Search the full catalogue for more? (7 more packages)(The groups are from the blueprint; the screen above is a sketch of the prototype’s two prompts.)
- The log viewer is pre-selected.
- Only packages that are published and compatible with the framework version being installed are offered. That’s why the list grows release by release without the installer changing.
- When you pick a package that has follow-up questions, they come right after, in both Recommended and Custom mode.
The same choices as flags, for CI or scripts:
npm create strutvane@latest my-app -- --features log-viewer,billing,search --feature-option billing.provider=paddle --yes--features none picks nothing. --feature-option <id>.<question>=<value> answers a picked package’s follow-up question; leave it out to take the package’s default.
How it works: one manifest, one index
Section titled “How it works: one manifest, one index”One manifest per package
Section titled “One manifest per package”Every package describes itself in a strutvane block in its own package.json. Reading it runs no code.
{ "name": "@strutvane/billing", "version": "0.2.0", "peerDependencies": { "@strutvane/framework": "^0.2" }, "strutvane": { "id": "billing", "name": "Billing", "description": "Subscriptions, plans and a customer portal", "category": "money", "tags": ["subscriptions", "stripe", "paddle"], "framework": "^0.2", "installs": { "config": ["config/billing.ts"], "env": ["BILLING_PROVIDER"], "migrations": true, "routes": true, "screens": true, "sidebar": ["Billing"] }, "questions": [ { "id": "provider", "label": "Billing: which payment provider?", "default": "stripe", "choices": [ { "value": "stripe", "label": "Stripe" }, { "value": "paddle", "label": "Paddle (merchant of record)" } ] } ], "docs": "https://vishwajit-vm.github.io/strutvane-docs/docs/latest/packages/billing/" }}Follow-up questions are declarative: a label, choices and a default, as data. Nothing from a package runs before it is installed.
One catalogue index
Section titled “One catalogue index”CI in the Strutvane hub builds one file, catalogue.json, from the published manifests. The installer, node strut install, node strut add, the package pages of these docs and the AI agent tools all read that one file, so a new package appears everywhere with no code change.
The index is treated as untrusted input. In the prototype:
- an entry with a bad shape is skipped, never offered;
- package names must be
@strutvane/<name>orstrutvane-<name>, so a name can’t sneak in a path like../; - a follow-up question that asks for a key, secret, token or password is refused: secrets are never typed into the installer, they go into
.envlater.
One conformance kit per kind of package
Section titled “One conformance kit per kind of package”Before a package can be listed, its CI must pass:
- the installer-protocol test (it installs itself completely, in any order);
- the security attack kit for its surface (for example tenancy, uploads or injection tests);
- a type-check against the current framework.
Designs also pass designConformance() (see Designs).
Versions
Section titled “Versions”- The core train moves in lockstep before 1.0: framework, auth, ui, the first-party designs, create-strutvane and the app skeleton all release the same version.
- Add-ons release on their own version numbers, with a peer range on the framework (
^0.2). The catalogue records which add-on versions work with which framework line.
Community packages
Section titled “Community packages”Community packages are named strutvane-<name>, use the same manifest and get a verified badge in the catalogue once they pass the same kits.
Every first-party package
Section titled “Every first-party package”These cards come from one data file (src/data/packages.json in the docs repository). The same file feeds this page, its Markdown export and the release notes, so a package can never be “planned” here and “retired” somewhere else. Every card says its status in words:
| Status | What it means |
|---|---|
| Available | Released on npm, with a stable version on latest. Nothing is available yet: 0.2 hasn’t been released. |
| Preview | Published for trying out (the next dist-tag); it may still change. |
| In development | Being built for the current line (phase 1, which is 0.2). |
| Planned | On the roadmap for a later phase. The installer offers it only once it’s published. |
| Shelved | Explored, then put aside. It may come back later. |
| Retired | No longer part of Strutvane. The card says what to use instead. |
A phase is a step of the roadmap: phase 1 is 0.2, phase 2 is 0.3, phase 3 leads to 1.0, and phases 4 to 8 come after 1.0. Use the two filters to narrow the list; each card links to its docs page and repository when they exist. Link to one package with its anchor, for example #pkg-auth.
Showing 60 of 60
Core
@strutvane/authIn developmentPhase 1Sign-in, registration, password reset, email verification, 2FA, passkeys, API tokens, teams and impersonation.
PageGuideRepositorySince 0.2
create-strutvaneIn developmentPhase 1The installer behind npm create strutvane@latest: questions, then a migrated, seeded app.
PageGuideRepositorySince 0.2
@strutvane/frameworkIn developmentPhase 1The framework: container, config, routing, controllers, validation, ORM, migrations, logging, authorization, tenancy and the node strut command line.
PageRepositorySince 0.2
strutvaneIn developmentPhase 1The small npx strutvane command: the same as node strut inside a project, a pointer to create one outside.
Which repository holds it is still open.
PageSince 0.2
@strutvane/uiIn developmentPhase 1The React admin's behaviour: auto CRUD screens, tables, forms, sidebar, command palette. The look comes from a design package.
PageRepositorySince 0.2
Designs
@strutvane/design-crispIn developmentPhase 1The default design: clean, minimal, quiet colours, dense readable tables.
Default in the installer. The look is proven as a mockup (spike 19).
@strutvane/design-vividIn developmentPhase 1A colourful design with soft-shadow cards, gradient charts and roomier spacing.
The look is proven as a mockup (spike 17).
Operations
@strutvane/log-viewerIn developmentPhase 1The logs screen at /_strutvane/logs: live tail, search and download. Logging itself is in the framework.
The repository is still named strutvane-logs; it is renamed to strutvane-log-viewer (ADR-0022).
PageRepositorySince 0.2
@strutvane/queue-dashboardPlannedPhase 2Jobs, failures, retries and scheduled tasks on one screen.
@strutvane/redisPlannedPhase 2Redis and Valkey drivers for cache, queue, locks, sessions, rate limits and broadcasting.
@strutvane/healthPlannedPhase 3Scheduled health checks, history, alerts and an uptime endpoint.
@strutvane/inspectorPlannedPhase 3A development recorder for requests, queries, jobs, mail and policy decisions.
@strutvane/observabilityPlannedPhase 3OpenTelemetry export and a self-hosted metrics dashboard.
@strutvane/backupPlannedPhase 4Encrypted database and storage backups, with restore drills.
Data
@strutvane/chartsPlannedPhase 3Chart and KPI widgets suggested from your tables, fed by a policy- and tenant-safe aggregate endpoint.
@strutvane/dashboardsPlannedPhase 3Dashboard pages, per-user layouts, filters and scheduled digests.
@strutvane/filesPlannedPhase 3S3 and Azure disks, presigned and resumable uploads, virus scanning and quotas.
@strutvane/import-exportPlannedPhase 3CSV and XLSX import with column mapping and a dry run; policy-aware exports.
@strutvane/searchPlannedPhase 3Meilisearch and Typesense engines, and hybrid vector search.
@strutvane/api-explorerPlannedPhase 4An interactive OpenAPI explorer with try-it-out.
@strutvane/graphqlPlannedPhase 5A GraphQL API generated from your models, policies and teams.
Back office
@strutvane/activity-logPlannedPhase 4Per-record change history, an activity feed and an audit explorer.
@strutvane/commentsPlannedPhase 4Threaded comments, mentions and reactions on any record.
@strutvane/media-libraryPlannedPhase 4Attachments, image conversions, responsive images and a media manager.
@strutvane/pdfPlannedPhase 4PDFs such as invoices and reports from React templates.
@strutvane/privacyPlannedPhase 4GDPR data export and erasure, consent and retention.
@strutvane/settingsPlannedPhase 4Typed, database-backed app, team and user settings with generated pages.
@strutvane/tagsPlannedPhase 4Team-scoped, typed tags on any model.
@strutvane/mail-templatesPlannedPhase 6Editable, per-team transactional mail templates.
@strutvane/resource-viewsPlannedPhase 6Kanban board and calendar views over any resource.
Identity
@strutvane/social-loginPlannedPhase 2Sign in with Google, Microsoft, GitHub and Apple.
Moved up to phase 2 (blueprint §10); the master list still says 5.
@strutvane/oauth-serverPlannedPhase 5An OAuth 2.1 provider, so other apps can sign in with yours.
@strutvane/ssoPlannedPhase 5Per-team OIDC and SAML single sign-on, SCIM and domain verification.
Integrations
@strutvane/feature-flagsPlannedPhase 5Typed feature flags per user, team or plan.
@strutvane/webhooksPlannedPhase 5Signed outgoing webhooks with retries, and verification of incoming ones.
@strutvane/notification-channelsPlannedPhase 6SMS, Slack, Teams, web push and WhatsApp next to email, with a preference centre.
@strutvane/realtimePlannedPhase 6A WebSocket server, channels and live tables.
@strutvane/geoPlannedPhase 8Spatial columns, distance queries, geocoding and map views.
Money
AI and automation
@strutvane/agent-toolsPlannedPhase 2AGENTS.md, skills, a local docs MCP server and offline docs search for AI coding assistants.
Moved up to phase 2 (blueprint §10); the master list still says 3.
@strutvane/mcp-serverPlannedPhase 5Lets AI agents use your app through MCP, under your policies and teams.
@strutvane/aiPlannedPhase 7AI model calls, structured output, embeddings and policy-bound agent tools.
@strutvane/workflowsPlannedPhase 7Durable workflows, approvals, timers and state machines.
Content
Testing
@strutvane/browser-testingPlannedPhase 7Playwright fixtures for testing the real UI in a browser.
Retired and shelved
design-glassShelvedA translucent "glass" design direction, explored as a mockup (spike 18).
Shelved on 2026-11-15 in favour of Crisp and Vivid. It is the first candidate for a future design package.
@strutvane/coreRetiredv1's kernel: container, providers, config, env, errors, events and hooks.
Use instead: @strutvane/framework/core
The repository was archived on GitHub on 2026-11-15. The npm name is deprecated with a pointer once framework v2 is published.
PageGuideRepositorySince 0.2
@strutvane/contractsRetiredv1's shared types and wire protocols.
Use instead: @strutvane/framework/contracts
The repository was archived on GitHub on 2026-11-15. The npm name is deprecated with a pointer once framework v2 is published.
PageGuideRepositorySince 0.2
@strutvane/cliRetiredv1's command line (the sv command).
Use instead: @strutvane/framework/console (run as node strut)
The repository was archived on GitHub on 2026-11-15. The npm name is deprecated with a pointer once framework v2 is published. The framework names this subpath console, not cli.
PageGuideRepositorySince 0.2
@strutvane/devkitRetiredv1's SDK for installers, generators and plugins.
Use instead: @strutvane/framework/devkit
The repository was archived on GitHub on 2026-11-15. The npm name is deprecated with a pointer once framework v2 is published.
PageGuideRepositorySince 0.2
@strutvane/logsRetiredv1's logging package: the pipeline and the viewer in one.
Use instead: Logging in @strutvane/framework (ADR-0022), plus @strutvane/log-viewer for the screen
PageGuideRepositorySince 0.2
launcherRetiredv1's separate launcher and release-channel logic (pnpm sv, @next-only starter).
Use instead: node strut (strut.js in the app) and npm create strutvane@latest
registry-compilerRetiredv1's registry compiler, which built the app from model files.
Use instead: Migrations as the source of truth, replayed into types and resources.json by node strut migrate
field-spec-parserRetiredv1's command-line field specs (title:string(120)) for generating models.
Use instead: Columns written in migrations with the Schema builder (node strut make:migration)
upgrade-mergeRetiredv1's upgrade command and its three-way merge of generated files.
Use instead: Owned files are never overwritten: auto() picks up new columns, and the upgrade guide lists every change
better-auth-defaultRetiredBetter Auth as v1's default identity engine.
Use instead: @strutvane/auth's own engine, with its tables as ordinary migrations in your app
The superseding ADR (for ADR-0005 and ADR-0013) is still to be written.
Common mistakes
Section titled “Common mistakes”“is not an available package”
Section titled ““is not an available package””These options do not work together: - --features "billing" is not an available package (unknown, unpublished, or not for this framework version). Search with: node strut add
Run with --help to see every option.Why: the id is misspelt, the package isn’t published yet, or it doesn’t support your framework version.
Fix: search the catalogue for the right id, and check the package’s phase above:
node strut addMy --feature-option is refused
Section titled “My --feature-option is refused”These options do not work together: - --feature-option billing.provider=braintree is not a choice. Use one of: stripe, paddle
Run with --help to see every option.Why: follow-up questions only accept the choices the package declares.
Fix: use one of the listed values:
npm create strutvane@latest my-app -- --features billing --feature-option billing.provider=paddle --yes“belongs to no picked feature with that question”
Section titled ““belongs to no picked feature with that question””These options do not work together: - --feature-option billing.provider belongs to no picked feature with that question
Run with --help to see every option.Why: you answered a question for a package you didn’t pick.
Fix: add the package to --features, or drop the option.
My options were ignored
Section titled “My options were ignored”Why: with npm create, flags before -- are kept by npm itself and never reach the installer.
Fix: put the installer’s flags after --:
npm create strutvane@latest my-app -- --features search --yesI edited a package’s files and lost my changes
Section titled “I edited a package’s files and lost my changes”Why: files under node_modules/ belong to npm and are replaced on every install or upgrade.
Fix: change the package’s behaviour through the files it copied into your app (config/<name>.ts, its migrations, owned screens) or through its documented options.
Next steps
Section titled “Next steps”- Installation: question 22 and every other installer question.
- Designs: the design packages.
@strutvane/log-viewer: the package every new app starts with.