Skip to main content
Weekly summaries of user-facing changes to Stars Components. For per-package history, see each package’s CHANGELOG.md in the monorepo, or the full release history.

2026-09-24

Nitro deploys, themed dev UI, and clearer diagnostics. This week also brings the http-framework 5.x release and a new @wolfstar/schema package.

New features

  • Nitro builds (experimental) — Set experimental.enableNitro to build your bot with Nitro v3. stars build outputs .output/ for the configured experimental.nitro.preset (node-server by default), so you can deploy to Cloudflare, AWS Lambda, Vercel, Netlify, Bun, Deno Deploy, and more. Install nitro and vite (Vite 8) as dev dependencies. See @wolfstar/cli.
  • Client.fetch() — @wolfstar/http-framework 5.0.0 adds client.fetch(request), the Web Request/Response counterpart of listen(). It runs the same signature verification and routing without binding a port, for Workers, Bun.serve, Deno.serve, and similar runtimes. See @wolfstar/http-framework.
  • stars dev colour themes — Press T in the interactive UI to pick dark, light, colour-blind friendly dark-daltonized/light-daltonized, terminal-palette dark-ansi/light-ansi, or auto. stars dev saves your choice between runs. Use --theme <name> or STARS_THEME to override it for one run.
  • varlock support (experimental) — @wolfstar/env-utilities 2.2.0 can load environment files with varlock instead of dotenv. Opt in with loader: 'varlock' or the DOTENV_LOADER environment variable. See Environment.
  • stars binary ships with http-framework — Installing @wolfstar/http-framework now gives you the stars command, with no separate @wolfstar/cli install.

Updates

  • Structured diagnostics — Config and CLI errors are now nostics diagnostics with stable codes, a reason, an actionable fix, and a docs link. ConfigError and CliError are removed. Catch errors with instanceof Diagnostic instead. Exit codes are unchanged. See Config errors and CLI errors.
  • Readable crash reports — Unexpected errors and stars dev startup crashes now render as sourcemapped, syntax-highlighted reports instead of raw stack traces.
  • Faster stars dev exit — The first Ctrl+C stops your bot gracefully. A second one kills the bot and its helper processes immediately, without waiting for dev.killTimeout.
  • New @wolfstar/schema package — The stars.config.* schema and loader now live in @wolfstar/schema. Imports from @wolfstar/http-framework/config keep working unchanged. If you install @wolfstar/cli without @wolfstar/http-framework, add @wolfstar/http-framework yourself. Scaffolded projects are unaffected.
  • Optional Vite and Nitro builders — The Vite and Nitro builders now ship as separate @wolfstar/vite-server and @wolfstar/nitro-server packages. They load only when you use them. Your CLI configuration is unchanged.
  • Oxc configs as TypeScript — @wolfstar/oxfmt-config and @wolfstar/oxlint-config 0.2.0 now default-export defineConfig objects. Spread the formatter config into oxfmt.config.ts and pass the linter config to extends in oxlint.config.ts. The index.json and .oxlintrc.json entry points are removed.
  • Plugins support http-framework 5 — @wolfstar/plugin-api, @wolfstar/plugin-i18next, @wolfstar/plugin-logger, and @wolfstar/plugin-subcommands-advanced now target @wolfstar/http-framework 5.x.

Bug fixes

  • stars dev readability on light terminals — The dev UI now uses semantic theme colours, so body text keeps your terminal’s foreground colour and stays readable on light backgrounds.

2026-09-17

Conventions land in the CLI: v4 is the new default, projects auto-register their plugins, and a quick tunnel now works out of the box.

New features

  • Convention-first stars workflow — Compatibility version 4 is now the default in @wolfstar/cli and @wolfstar/http-framework. stars dev forces development mode, src/locales is copied and watched automatically, and environment files are discovered under both src/ and the project root. The interactive dev UI adds a t shortcut to open or close a public quick tunnel without configuring dev.tunnel.
  • Auto-registered WolfStar plugins — Bundler builds now inject the /register side-effect entrypoint of every installed @wolfstar/plugin-* dependency before your app entry, so plugins activate without manual import '@wolfstar/plugin-x/register' lines. See Plugins.
  • Generated TypeScript alias config — stars prepare, stars dev, and stars build write an extendable .stars/tsconfig.json whose paths match the tsdown aliases. Scaffolded projects extend it and pick up Sapphire base, extra-strict, and decorators options automatically. See @wolfstar/create-http-framework.

Updates

  • HTTP-framework 4.0.x — Structured, leveled logging replaces raw console calls for HMR events and command-router warnings. @wolfstar/env-utilities 2.1.x follows the same move, using container.logger from @sapphire/pieces when available and falling back to console.debug for standalone consumers.

Bug fixes

  • Quick tunnel reliability — dev.tunnel now opens the cloudflared tunnel through untun instead of spawning cloudflared and scraping stdout. untun manages the binary (downloading it if missing) and exposes the URL and lifecycle programmatically, which also fixes the tunnel never closing when the spawn failed silently.
  • @wolfstar/shared-http-pieces — Consumer locale paths are preserved and the bundled commands/shared namespace loads correctly when using the register entrypoint. See @wolfstar/shared-http-pieces.
  • @wolfstar/plugin-subcommands-advanced — Subcommand builder callbacks are now deferred until every command piece has been constructed, fixing crashes when builders referenced not-yet-loaded siblings. See @wolfstar/plugin-subcommands-advanced.