@fonderie/vue-admin-screens

@fonderie/vue-admin-screens

The admin shell for Vue — the /wp-admin of a Fonderie app, over @fonderie/admin. Navigation follows the operator's questions; each page is a screen you can also mount on its own.

Status: experimental (0.x).

import { AdminClient, AuditAdminClient, AuthAdminClient, BillingAdminClient, ConfigAdminClient, CourierAdminClient } from '@fonderie/client';
import { AdminShell } from '@fonderie/vue-admin-screens';

const base = { baseUrl: 'https://api.example.com', adminToken, actor: 'louis' };
const client = new AdminClient(base);
// prefix: the composed surface under /_admin — one token for everything.
const configClient = new ConfigAdminClient({ ...base, prefix: '/_admin' });
const courierClient = new CourierAdminClient({ ...base, prefix: '/_admin' });
const authClient = new AuthAdminClient(base); // @fonderie/auth ≥ 7.8
const billingClient = new BillingAdminClient(base); // @fonderie/billing ≥ 9.10
const auditClient = new AuditAdminClient(base); // @fonderie/audit ≥ 5.2

h(AdminShell, { client, configClient, courierClient, authClient, billingClient, auditClient })

Pass page and listen to navigate to own the URL (one route per page); omit page and the shell keeps it itself. Settings and Messaging appear only when their client is given.

Give the shell a read token, not the root one. With @fonderie/admin ≥ 0.6 the configured adminToken is the root — every scope, including the plaintext secret reveal, and the only credential that can mint or revoke. Issue a scoped one for the dashboard (fonderie admin token issue dashboard --scopes read, or the Access page itself) and hand the shell that. The Access page then shows issuing as unavailable, which is the point.

Nothing here stores the token: the app constructs the clients and decides where the token lives. Every request through the shell lands in the admin log, including the ones the token refuses.