> ## Documentation Index > Fetch the complete documentation index at: https://stars-components.js.org/llms.txt > Use this file to discover all available pages before exploring further. # @wolfstar/vite-server > Changelog for @wolfstar/vite-server: the optional Vite builder for stars. Changes to [`@wolfstar/vite-server`](https://stars-components.js.org/documentation/packages/vite-server). For the weekly summary across all packages, see the [changelog overview](https://stars-components.js.org/documentation/changelog/index.md). ## `0.5.2` (2026-10-21) ### Updates * **Dev server bind address** — The Vite dev server binds to the address from `dev.env` before falling back to the hostname of `dev.url`, so it follows `stars dev --host`. ([#348](https://github.com/wolfstar-project/stars-components/pull/348)) ## `0.5.1` (2026-10-18) ### Updates * **Dependencies** — Updated `@wolfstar/schema` to `0.12.0`. ## `0.5.0` (2026-10-17) ### New features * **`ctx.addPiecesDir(directory)`** — Modules can register a directory of pieces, with one folder per store (`commands`, `listeners`, …). The pieces are registered before the bot loads, including for `tsc` and `none` builds. `ModulesRuntime` gains `piecesDirs`, `stars info` lists them, and a relative path fails with `MODULE_PIECES_INVALID`. ([#335](https://github.com/wolfstar-project/stars-components/pull/335)) * **Client lifecycle hooks** — `hooks` in `defineModule` accepts `client:preGenericsInitialization`, `client:preInitialization`, `client:postInitialization`, `client:preLoad`, and `client:postListen`. Give each hook by source (`{ from, export }`), a function called with `(client, clientOptions)`. `ctx.addClientHook(name, source)` does the same from `setup`. A module's hooks share one runtime plugin named after it. `ModulesRuntime` gains `clientHooks`, `stars info` lists them, and a bad hook fails with `MODULE_HOOK_INVALID`. ([#337](https://github.com/wolfstar-project/stars-components/pull/337)) * **`ctx.addLocales(directory)`** — Modules can add a directory of locales laid out as `/.json`. The locales merge into the client's `i18n` option before `@wolfstar/plugin-i18next` builds its handler, and your project's own languages directory is kept. `ModulesRuntime` gains `locales`, `stars info` lists them, and a bad directory fails with `MODULE_LOCALES_INVALID`. ([#339](https://github.com/wolfstar-project/stars-components/pull/339)) * **`future.compatibilityVersion: 7`** — Opt in to let `stars.config` decide what registers. `@wolfstar/plugin-*` packages in `package.json` are no longer activated by their name. Only the modules in `modules`, and the ones they install, are. `stars build`, `prepare`, `dev`, `info`, and `doctor` warn with `PLUGINS_NOT_REGISTERED` about an installed plugin that is left out. ([#338](https://github.com/wolfstar-project/stars-components/pull/338)) ### Updates * **Dependencies** — Updated `@wolfstar/schema` to `0.11.0`. ## `0.4.5` (2026-10-09) ### Updates * **Dependencies** — Updated `@wolfstar/schema` to `0.10.0`. ## `0.4.4` (2026-10-07) ### Updates * **Dependencies** — Updated `@wolfstar/schema` to `0.9.0`. ## `0.4.3` (2026-10-06) ### Updates * **Dependencies** — Updated `@wolfstar/schema` to `0.8.0`. ## `0.4.2` (2026-10-06) ### Updates * **Dependencies** — Updated all non-major dependencies. Updated `@wolfstar/schema` to `0.7.0` ([#253](https://github.com/wolfstar-project/stars-components/pull/253)). ## `0.4.1` (2026-10-04) ### Updates * **Dependencies** — Updated `@wolfstar/schema` to `0.6.0`. ## `0.4.0` (2026-10-02) ### New features * **Stars modules** — Add `modules` to `stars.config` as a list of package names or `[name, options]` tuples. The CLI installs them with `@wolfstar/kit`'s `setupModules` before the `config:resolved` hook, and the resolved configuration gains `modules` and `runtime` (the runtime plugins and auto-import presets the modules contribute). Runtime plugins are registered in your bot before the legacy `/register` imports, which skip packages listed in `modules`. With the `tsc` and `none` build tools, `stars dev` preloads them with `node --import`, and `stars prepare` writes `.stars/modules.mjs` for production. `stars build`, `stars prepare`, and `stars info` warn with `MODULES_PRELOAD_REQUIRED` when you need that preload. A failing module is reported as a `MODULE_FAILED` diagnostic (exit code 2). See [`@wolfstar/kit`](https://stars-components.js.org/documentation/packages/kit). [#247](https://github.com/wolfstar-project/stars-components/pull/247) ### Updates * **Dependencies** — Updated `@wolfstar/schema` to `0.5.0`. ## `0.3.0` ### New features * **`env` in `stars.config`** — Added a top-level `env` option that mirrors the setup options from `@wolfstar/env-utilities`. When present, the built entry automatically imports it first, before plugin registrations and the bot's own modules. * **Lifecycle hooks** — Added Nuxt-style hooks (`config:resolved`, `env:options`, `prepare:*`, `builder:created`, `tsdown:options`, `build:*`, `dev:*`) powered by `hookable`. ### Migration * `future.compatibilityVersion: 5` is now the default. It is version 4 plus the automatic `env` registration, which activates when the project depends on `@wolfstar/env-utilities` and stays off with Nitro. Version 4 is still supported. Version 3 is end of life: it still works but now reports a `COMPATIBILITY_VERSION_EOL` warning and will be removed in the next major. * Projects generated by `@wolfstar/create-http-framework` with the `tsdown` or `vite` build no longer call `setup()` from `@wolfstar/env-utilities` by hand. `tsc` and JavaScript projects keep it and set `env: false` ([#243](https://github.com/wolfstar-project/stars-components/pull/243)). ### Updates * **Dependencies** — Updated `@wolfstar/schema` to `0.4.0`. ## `0.2.4` ### Updates * **Dependencies** — Updated `@wolfstar/schema` to `0.3.0`. ## `0.2.3` ### Updates * **Dependencies** — Updated all non-major dependencies. Updated `@wolfstar/schema` to `0.2.1` ([#227](https://github.com/wolfstar-project/stars-components/pull/227)). ## `0.2.2` ### Bug fixes * **Only register plugins with `/register`** — `stars build`/`stars dev` now only auto-registers installed `@wolfstar/plugin-*` packages that export a `/register` entrypoint. Library packages such as `@wolfstar/plugin-cache`, `@wolfstar/plugin-gateway` and `@wolfstar/plugin-sharder` no longer break the build ([#217](https://github.com/wolfstar-project/stars-components/issues/217)) ([#222](https://github.com/wolfstar-project/stars-components/pull/222)). ## `0.2.1` ### Updates * **Dependencies** — Updated all non-major dependencies ([#213](https://github.com/wolfstar-project/stars-components/pull/213)). ## `0.2.0` ### New features * **Separate Vite builder package** — The optional Vite builder is now a dedicated server package with a shared host context and builder lifecycle contract in [`@wolfstar/schema`](https://stars-components.js.org/documentation/changelog/stars-components/schema). CLI configuration, lazy loading, project-local dependencies, and plugin registration are preserved ([#209](https://github.com/wolfstar-project/stars-components/pull/209)). ### Updates * **Dependencies** — Updated `@wolfstar/schema` to `0.2.0`. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.