@authup/client-account-console
v1.0.0-beta.68
Published
Authup's account console: the end-user self-service SPA, served by server-core at /console/account and hostable standalone.
Maintainers
Readme
@authup/client-account-console 👤
This is the account console for Authup: the end-user self-service surface (profile, password, authenticators, sessions, application consents).
It is a client-only single-page application. The authup server
(@authup/server-core) depends on this package and serves the built
bundle at <publicUrl>/console/account; the same bundle can be hosted standalone
on any static host. See the deployment guide for details, including the
runtime configuration contract (window.__AUTHUP__ via the
<!--account-config--> marker in index.html).
Development
The dev server needs a running authup server to talk to.
Start (or pick) an authup server. Outside production the vite origin (
http://localhost:5173) is seeded into the trusted origins already, so the per-realmaccount-consoleOAuth2 client accepts the sign-in round-trip with no configuration:authup startFrom the repository, after
npm run build:npm run cli -w apps/server-core -- startOnly one standalone console can hold the port, so if the admin console's dev server already has it, run this one through
authup devinstead or give it its ownTRUSTED_ORIGINSentry.Run the dev server with the API URL injected:
VITE_API_URL=http://localhost:3000 npm run dev(
VITE_API_URLcan also live in a local.env.local. Without it the app assumes it is served by the authup origin itself and derives the API URL from its own location, which is wrong under the vite dev server.)Open http://localhost:5173/console/account — the app is mounted under its canonical
/console/accountbase path in dev too.
Sign-in leaves the dev origin for the server's hosted login and returns with an authorization code, so the full flow works against the real API.
Build
npm run buildEmits the static bundle to dist/ (the artifact this package ships).
License
Made with 💚
Published under the AGPL-3.0 License. A commercial license is available for organizations that cannot meet the AGPL's conditions — see LICENSING.md or contact [email protected].
