absolute config

A local visual editor for your project's configuration — tune absolute.config.ts, package.json, ESLint, tsconfig, and Prettier, plus manage Integrations and Auth, from a browser UI that writes changes straight back to your files.

#Usage

absolute config starts a local server and opens (with --open) a visual editor for the config files in your project. Use --port to choose the port, --config to point at a specificabsolute.config.ts, and --no-https to serve over plain HTTP. Every change is spliced back into the real file through the TypeScript compiler API, so your imports, comments, and formatting survive — only serializable values are editable, and fields whose value is code (a store, a callback) are shown read-only so the UI never clobbers them.

BASH

# Open the Absolute Config visual editor in your browser
absolute config

# Pick the port and open it automatically
absolute config --port 4099 --open

# Point at a specific config file
absolute config --config ./absolute.config.ts

absolute config

$ absolute config
  ABSOLUTEJS v0.19.0-beta  ready in 283ms

  ➜  Local:   https://config.absolute.localhost:4099/

  Open it in your browser, or pass --open.

#Panels

The sidebar groups the editor into Project and Integrations. The Project panels each edit one config file: absolute.config (the defineConfig fields, introspected from the framework's build config), package.json (scripts & metadata), ESLint (rules & severities), tsconfig (compiler options), and Prettier (formatting). Each renders schema-driven inputs rather than raw JSON, and writes are minimal, targeted splices — never a full-file reformat.

#Integrations

The Integrations panel is the home for the official Elysia plugins. openapi and telemetry are config-driven — toggling them flips the field in absolute.config.ts that the runtime reads to mount them — while cors, jwt, and cron install the package and hand you the exact .use(...) to drop into your server. It's the same engine as absolute add <plugin>, just with a button. The JWT card is deliberately framed as a token primitive (signing your own API tokens) and cross-links to the Auth panel for actual user authentication.

#Auth

The Auth panel introspects your @absolutejs/auth setup: it AST-scans for your auth() call to show the installed version, which of the sixteen features (credentials, MFA, SSO, SCIM, passkeys, organizations, …) are configured, and the always-on core OAuth2 routes. From there it's a wizard + dashboard hybrid — edit the serializable settings (route paths, session durations, limits) through an auth.config.ts created with defineAuthSettings, and scaffold a feature's code wiring (store + hook stubs) with one click, the same as absolute add auth:<feature>.

PreviousAdd / Remove NextDatabase