> ## 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/plugin-subcommands-advanced

> Changelog for @wolfstar/plugin-subcommands-advanced: advanced subcommand builders.

Changes to [`@wolfstar/plugin-subcommands-advanced`](https://stars-components.js.org/documentation/packages/plugin-subcommands-advanced). For the weekly summary across all packages, see the [changelog overview](https://stars-components.js.org/documentation/changelog/index.md).

## `2.3.0` (2026-10-20)

### New features

* **Own `stars.config` key** — The module sets `meta.configKey`, so you can write its options under the top-level `subcommandsAdvanced` key of `stars.config` instead of the `[specifier, options]` tuple of `modules`. The tuple still works and is merged over the key. The key is typed in `defineConfig` once the module is imported in `stars.config.ts`. `subcommandsAdvanced` takes no options yet and only reserves its name. ([#259](https://github.com/wolfstar-project/plugins/pull/259))

### Updates

* **New optional peer** — `@wolfstar/schema` (`^0.9.0`) is a new optional peer that carries the `StarsConfig` type the keys extend.

### Migration

* **`@wolfstar/kit` peer raised** — The `@wolfstar/kit` peer range moves from `^0.1.0` to `^0.2.0`, the first version that reads `configKey`. If your project uses `@wolfstar/kit` 0.1, update it.

## `2.2.1` (2026-10-17)

### Bug fixes

* **Stable subcommand order** — Modular subcommands and groups now register sorted by name instead of in store load order, which changed between starts. `@wolfstar/http-framework` compares deployed commands by position, so every parent with modular subcommands used to update on each start. The first start after upgrading may update those commands once. Subcommands the parent declares itself keep their place before the registered ones. ([#257](https://github.com/wolfstar-project/plugins/pull/257))

## `2.2.0` (2026-10-08)

### New features

* **`Command.OptionsOf` and `Subcommand.OptionsOf`** — Re-export the framework's `Command.OptionsOf`, so command classes that import `Command` from this package can type their generated options (`stars codegen`). Requires `@wolfstar/http-framework` 6.2.0 or later for the type. ([#231](https://github.com/wolfstar-project/plugins/pull/231))

## `2.1.0` (2026-10-05)

### New features

* **`/module` and `/plugin` entrypoints** — Adds `@wolfstar/plugin-subcommands-advanced/module` and `@wolfstar/plugin-subcommands-advanced/plugin`. List the module in `modules` in `stars.config`, or pass the `definePlugin` factory to `plugins`. Both need `@wolfstar/http-framework` 6.1 (and `@wolfstar/kit` for the module). `./register` is unchanged and still supports framework v3, v5, and v6. ([#193](https://github.com/wolfstar-project/plugins/pull/193))

## `2.0.6` (2026-10-04)

### Updates

* **`http-framework` 6 support** — The peer range now accepts [`@wolfstar/http-framework`](https://stars-components.js.org/documentation/changelog/stars-components/http-framework) `^6.0.0`. ([#176](https://github.com/wolfstar-project/plugins/pull/176))

### Bug fixes

* **Peer range** — Accept `@wolfstar/http-framework` v6 in the peer range (`|| ^6.0.0`). ([#176](https://github.com/wolfstar-project/plugins/pull/176))

## `2.0.5`

### Bug fixes

* **Peer dependency** — Accept `@wolfstar/http-framework` v5 as a peer dependency (`^3.1.0 || ^5.0.0`), so v5 projects no longer install the plugin with an unmet peer. ([#125](https://github.com/wolfstar-project/plugins/pull/125))

## `2.0.4` (2026-09-17)

### Bug fixes

* **Deferred builder callbacks** — Subcommand builder callbacks are now deferred until every command piece has been constructed, fixing crashes when builders referenced not-yet-loaded siblings. ([#83](https://github.com/wolfstar-project/plugins/pull/83))
* **Dependencies** — Updated all non-major dependencies. ([#75](https://github.com/wolfstar-project/plugins/pull/75))

## `2.0.3`

### Updates

* **Type validation** — Validate every published subpath export with `are-the-types-wrong`, not just the main entrypoint. `createTsdownOptions` hardcoded `attw.entrypoints` to `["."]`, so the `./register` export of each package shipped unchecked. It now accepts an `attwEntrypoints` option, and all packages list their real entrypoints. ([#70](https://github.com/wolfstar-project/plugins/pull/70))

## `2.0.2`

### Updates

* **Dependencies** — Updated all non-major dependencies. ([#47](https://github.com/wolfstar-project/plugins/pull/47))

## `2.0.1`

### Updates

* **Dependencies** — Updated all non-major dependencies. ([#26](https://github.com/wolfstar-project/plugins/pull/26))

### Bug fixes

* **Registry registration** — Fix `RegisterAsSubcommand` and `RegisterAsSubcommandGroup` not registering the decorated subcommand piece in `applicationCommandRegistry`, which prevented modular subcommand classes from being recognized as application commands. ([#30](https://github.com/wolfstar-project/plugins/pull/30))

## `2.0.0`

### New features

* **New package** — Add `@wolfstar/plugin-subcommands-advanced`: modular slash subcommands as separate command classes for `@wolfstar/http-framework`, adapted from `@kaname-png/plugin-subcommands-advanced`. ([#17](https://github.com/wolfstar-project/plugins/pull/17))

## `1.0.0`

### New features

* **Initial release** — Modular slash subcommands as separate command classes for `@wolfstar/http-framework`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.