@wolfstar/schema 0.2.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2022 Wolfstar Project
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,58 @@
+<div align="center">
+  <picture>
+    <img src="https://cdn.wolfstar.rocks/wolfstar-assets/stars-components/wordmark.webp" alt="Stars Components" width="440" />
+  </picture>
+
+# @wolfstar/schema
+
+**Typed `stars.config.*` schema and loader shared by `@wolfstar/http-framework` and `@wolfstar/cli`.**
+
+[![version](https://npmx.dev/api/registry/badge/version/@wolfstar/schema)](https://npmx.dev/package/@wolfstar/schema)
+[![downloads](https://npmx.dev/api/registry/badge/downloads/@wolfstar/schema)](https://npmx.dev/package/@wolfstar/schema)
+[![license](https://img.shields.io/github/license/wolfstar-project/stars-components?style=flat-square&color=informational)](https://github.com/wolfstar-project/stars-components/blob/main/LICENSE)
+
+</div>
+
+## Description
+
+The `defineConfig` helper, the `StarsConfig` schema, and the `stars.config.{ts,mts,cts,js,mjs,cjs}` loader/validator,
+in their own package so `@wolfstar/http-framework` and `@wolfstar/cli` can each depend on it without depending on
+each other — the way `@nuxt/schema` sits between `nuxt` and `@nuxt/cli`.
+
+This module is intentionally tiny and side-effect free: importing it from a `stars.config.ts` file must never start
+a bot nor pull in the CLI's runtime.
+
+`@wolfstar/http-framework` re-exports this package's public surface from `@wolfstar/http-framework/config`, so
+existing `import { defineConfig } from '@wolfstar/http-framework/config'` code keeps working unchanged — most
+projects should keep importing it from there rather than depending on this package directly. See the
+[`@wolfstar/http-framework` README](../http-framework#project-configuration-starsconfig) for the full configuration
+reference.
+
+## Usage
+
+```typescript
+// stars.config.ts
+import { defineConfig } from '@wolfstar/schema';
+
+export default defineConfig({});
+```
+
+## Package structure
+
+- `src/types/config.ts` defines the public input types without runtime dependencies.
+- `src/config.ts` provides the identity helper and type exports. The `@wolfstar/schema/config` entry is suitable
+  for configuration files that only need `defineConfig`, without loading filesystem resolution or diagnostics.
+- `src/config/` owns discovery, validation, defaults, and resolution.
+- `src/index.ts` preserves the complete public API, including the helper and loader.
+
+The framework exposes package-root `config.js`/`config.d.ts` and `schema.js`/`schema.d.ts` facades, following
+[Nuxt's package layout](https://github.com/nuxt/nuxt/tree/main/packages/nuxt). Both forward this package unchanged
+for backwards compatibility. The CLI depends directly on this package, keeping the dependency graph acyclic.
+
+## Server integrations
+
+Stars separates the optional integrations into [`@wolfstar/vite-server`](../vite-server) and
+[`@wolfstar/nitro-server`](../nitro-server), following Nuxt's server package boundaries.
+Both implement the `Builder` contract exported by this schema package. The CLI loads them on demand and supplies
+a `BuilderContext` for project dependency resolution and plugin registration, so neither integration depends on
+the CLI or framework runtime. Process supervision and the external-build watcher remain in the CLI.

package/dist/esm/config.d.ts

@@ -0,0 +1,398 @@
+//#region src/types/config.d.ts
+/**
+ * The build tool used to turn the project sources into runnable JavaScript.
+ *
+ * - `tsdown`: run the project's own `tsdown` programmatically, configured from {@link StarsConfig.tsdown} (and, with
+ *   {@link StarsFutureConfig.compatibilityVersion} `3`, from the project's `tsdown.config.*` too).
+ * - `tsc`: run the project's `tsc -b` on the configured `tsconfig`.
+ * - `vite`: run the project's own `vite` (configuration file included), requires `experimental.enableVite`.
+ * - `none`: the entry is runnable as-is (JavaScript projects), no build step.
+ * - `auto`: detect from the project (default).
+ */
+type StarsBuildTool = 'tsdown' | 'tsc' | 'none' | 'vite';
+interface StarsBuildConfig {
+  /**
+   * The build tool to use.
+   * @default 'auto'
+   */
+  tool?: StarsBuildTool | 'auto';
+  /**
+   * The directory, relative to {@link StarsConfig.root}, the build writes into.
+   * @default 'dist', or '.output' when `experimental.enableNitro` is on (Nitro's own convention)
+   */
+  outDir?: string;
+  /**
+   * The `tsconfig.json` the `tsc` and `tsdown` build tools use, relative to {@link StarsConfig.root}.
+   * @default 'src/tsconfig.json' when it exists, 'tsconfig.json' otherwise
+   */
+  tsconfig?: string;
+}
+/**
+ * Raw options merged into the project's own `vite.config.*`, the way `vite: {}` in a Nuxt config is merged into
+ * Nuxt's own Vite config. Kept as `unknown` here (the CLI, not the framework, depends on `vite`'s types) and passed
+ * to Vite's `mergeConfig` as-is.
+ */
+type StarsViteConfig = Record<string, unknown>;
+/**
+ * Options for `tsdown`, the bundler `stars build` uses by default.
+ *
+ * With {@link StarsFutureConfig.compatibilityVersion} `4` these replace `tsdown.config.*` outright: the build is
+ * derived from `stars.config` (the entry's directory, `build.outDir`, `build.tsconfig`) and these options are layered
+ * on top, so a project keeps one configuration file instead of two. With `3` the project's own `tsdown.config.*` is
+ * still loaded and these are merged over it, the way `vite: {}` in a Nuxt config is merged into the project's own
+ * Vite config: values here win, and `plugins` are appended rather than replaced.
+ *
+ * The options named below are the ones a bot usually reaches for. Every other `tsdown` option is accepted as-is —
+ * the framework does not depend on `tsdown`, so they stay loosely typed here and `tsdown`'s own `UserConfig` is the
+ * reference.
+ */
+interface StarsTsdownConfig {
+  /** Entry files or glob patterns, relative to the project root. Defaults to every source file next to `entry`. */
+  entry?: string | readonly string[] | Record<string, string>;
+  /** @default 'esm' */
+  format?: 'esm' | 'cjs' | 'iife' | 'umd' | readonly string[] | Record<string, unknown>;
+  /** @default 'node' */
+  platform?: 'node' | 'neutral' | 'browser';
+  target?: string | readonly string[] | false;
+  /**
+   * Emits one output file per source file instead of a single bundle, so pieces stay loadable from `dist/commands`
+   * and friends at runtime.
+   * @default true
+   */
+  unbundle?: boolean;
+  /** Rolldown plugins. Appended to the ones `stars` adds (auto imports) and to those of a `tsdown.config.*`. */
+  plugins?: readonly unknown[];
+  alias?: Record<string, string>;
+  define?: Record<string, string>;
+  external?: unknown;
+  noExternal?: unknown;
+  deps?: Record<string, unknown>;
+  /** @default () => ({ js: extname(build.output) }) */
+  outExtensions?: unknown;
+  /** @default true */
+  sourcemap?: boolean | 'inline' | 'hidden';
+  minify?: unknown;
+  /** @default false — a bot is not a library, so no declaration files are emitted. */
+  dts?: boolean | Record<string, unknown>;
+  /** @default true */
+  clean?: boolean | readonly string[];
+  treeshake?: boolean;
+  copy?: unknown;
+  hooks?: Record<string, unknown>;
+  [option: string]: unknown;
+}
+/**
+ * The build-default generation the project runs on. Version 4 is current; version 3 remains available for projects
+ * that still load a standalone `tsdown.config.*`.
+ */
+type StarsCompatibilityVersion = 3 | 4;
+/**
+ * Nuxt-style compatibility block. New projects need not set it; version 3 is retained as an explicit migration
+ * escape hatch for projects that still use a standalone `tsdown.config.*`.
+ */
+interface StarsFutureConfig {
+  /**
+   * The major whose defaults apply.
+   *
+   * `4` is the default build pipeline:
+   * - auto imports are on by default with the `tsdown` build tool ({@link StarsImportsConfig}), and the
+   *   `autoImports()` plugin is wired into the build by `stars` itself.
+   * - `tsdown` is configured from {@link StarsConfig.tsdown} only. A `tsdown.config.*` in the project root is
+   *   rejected rather than silently ignored, so a build never loses the plugins it declares.
+   * - `build.tool: 'auto'` resolves to `tsdown` for any TypeScript entry, without looking for a `tsdown.config.*`
+   *   or a `tsdown` dependency first.
+   *
+   * `3` keeps the legacy behaviour: auto imports off unless asked for, and a `tsdown.config.*` loaded and merged with
+   * {@link StarsConfig.tsdown}.
+   * @default 4
+   */
+  compatibilityVersion?: StarsCompatibilityVersion;
+}
+/**
+ * The type checker `stars dev` runs next to the bot.
+ *
+ * - `tsc`: the project's own TypeScript, in watch mode.
+ * - `golar`: the project's `golar`, forwarding to TypeScript (`golar tsc`), in watch mode.
+ * - `tsz`: the project's `tsz` (or `try-tsz`). It has no watch mode, so it is re-run after every build instead.
+ * - `auto`: `golar` when the project depends on it, `tsc` otherwise (default).
+ */
+type StarsTypechecker = 'tsc' | 'golar' | 'tsz';
+interface StarsTypecheckConfig {
+  /**
+   * The `tsconfig.json` the type checker runs against, relative to {@link StarsConfig.root}.
+   * @default the build tool's tsconfig, 'src/tsconfig.json' or 'tsconfig.json'
+   */
+  tsconfig?: string;
+  /**
+   * Which type checker to run.
+   * @default 'auto'
+   */
+  checker?: StarsTypechecker | 'auto';
+}
+interface StarsTunnelConfig {
+  /**
+   * An https URL you already serve; when unset a `cloudflared` quick tunnel is opened instead.
+   */
+  url?: string;
+  /**
+   * Writes the tunnel's URL to the Discord application's `interactions_endpoint_url` when it changes.
+   *
+   * This edits a live Discord application, so it is opt-in: it needs `DISCORD_TOKEN` and `DISCORD_APPLICATION_ID`
+   * (or `APPLICATION_ID`) in the environment or the project's `.env`.
+   * @default false
+   */
+  updateEndpoint?: boolean;
+  /**
+   * The path the interactions endpoint is served on, appended to the tunnel URL.
+   * @default '/'
+   */
+  path?: string;
+}
+interface StarsDevConfig {
+  /** Custom terminal wordmark (one or more lines), or `false` to hide it. Defaults to the Stars wordmark. */
+  banner?: string | readonly string[] | false;
+  /**
+   * Extra paths to watch, relative to {@link StarsConfig.root}. Only used when
+   * the build tool is `none`; `tsdown` and `tsc` watch through their own build.
+   * @default [dirname(entry)]
+   */
+  watch?: string[];
+  /**
+   * Glob patterns or paths to ignore while watching, relative to {@link StarsConfig.root}.
+   * @default ['**\/node_modules/**', '**\/dist/**', '**\/.git/**']
+   */
+  ignore?: string[];
+  /**
+   * Milliseconds to wait after a change before restarting the bot.
+   * @default 150
+   */
+  debounce?: number;
+  /**
+   * Environment variables added to the bot process.
+   */
+  env?: Record<string, string>;
+  /**
+   * Arguments passed to `node` before the entry file.
+   * @default ['--enable-source-maps']
+   */
+  nodeArgs?: string[];
+  /**
+   * Arguments passed to the bot after the entry file.
+   * @default []
+   */
+  args?: string[];
+  /**
+   * The URL the bot listens on, shown in the dev UI's status line and used for {@link StarsDevConfig.health}.
+   *
+   * Resolved automatically, the way Vite's and Nuxt's dev servers do, from (in order) `dev.env.HTTP_PORT`, the
+   * process's `HTTP_PORT`, the project's `src/.env*`/`.env*` (`HTTP_PORT` or `PORT`), or `3000`. `stars dev` also
+   * resolves whether `localhost` should be shown as `127.0.0.1` instead, the same DNS-order check Vite does, so the
+   * printed URL is always the one that is actually reachable.
+   * @default `http://localhost:3000` (or whichever port is found)
+   */
+  url?: string;
+  /**
+   * A path, relative to {@link StarsDevConfig.url}, polled to report the bot's health in the dev UI.
+   * When unset the dev UI only reports process state.
+   */
+  health?: string;
+  /**
+   * Milliseconds to wait for the bot to exit after `SIGTERM` before killing it.
+   * @default 5000
+   */
+  killTimeout?: number;
+  /**
+   * Runs a type checker next to the bot and reports type errors on the dev UI's `tsc` channel, without blocking
+   * builds or restarts. `true` uses the project's own tsconfig and type checker, an object picks either
+   * ({@link StarsTypecheckConfig.checker}).
+   * @default false
+   */
+  typecheck?: boolean | StarsTypecheckConfig;
+  /**
+   * Exposes the bot's HTTP interactions endpoint publicly while `stars dev` runs, so Discord can reach it.
+   *
+   * `true` opens a `cloudflared` quick tunnel (its hostname changes on every run), a string is an https URL you
+   * already serve yourself (named tunnel, reverse proxy, …) that the CLI only checks for reachability.
+   * @default false
+   */
+  tunnel?: boolean | string | StarsTunnelConfig;
+  /**
+   * The file `stars dev` mirrors its logs into, relative to {@link StarsConfig.root}, so a session can be read back
+   * after the terminal UI is gone. `false` disables it.
+   * @default '.stars/dev.log'
+   */
+  logFile?: string | false;
+}
+interface StarsI18nCodegenConfig {
+  /**
+   * The base locale directory, relative to {@link StarsConfig.root}.
+   * @default 'src/locales/en-US'
+   */
+  locales?: string;
+  /**
+   * The generated declaration file, relative to {@link StarsConfig.root}.
+   * @default 'src/@types/i18next.d.ts'
+   */
+  output?: string;
+}
+interface StarsCodegenConfig {
+  /**
+   * i18next type generation through `@wolfstar/i18next-type-generator`.
+   * `false` disables it, an object enables it, unset auto-detects from the presence of the locales directory.
+   */
+  i18n?: StarsI18nCodegenConfig | false;
+}
+interface StarsImportsConfig {
+  /**
+   * Whether auto imports are enabled. Requires the `tsdown` build tool: the imports are injected at build time by
+   * the `autoImports()` plugin from `@wolfstar/http-framework/auto-imports`, which the other tools cannot run.
+   * @default true when the build tool is 'tsdown', false otherwise
+   */
+  enabled?: boolean;
+  /**
+   * Directories, relative to {@link StarsConfig.root}, whose exported values are auto-importable. Entries are glob
+   * path patterns: `'src/lib'` scans only the files directly inside it, `'src/lib/**'` scans recursively.
+   * @default ['src/lib/**', 'src/utils/**']
+   */
+  dirs?: string[];
+  /**
+   * Packages whose exports are auto-importable. Packages that are not installed are skipped.
+   * @default ['@wolfstar/http-framework', '@wolfstar/env-utilities']
+   */
+  presets?: string[];
+  /**
+   * Export names excluded from auto imports, e.g. to avoid clashes with project-local names.
+   * @default []
+   */
+  exclude?: string[];
+  /**
+   * The generated declaration file that types the auto imports, relative to {@link StarsConfig.root}.
+   * Include it in the project's tsconfig and add its directory to .gitignore.
+   * @default '.stars/imports.d.ts'
+   */
+  dts?: string;
+}
+/**
+ * The [Nitro preset](https://nitro.build/deploy) `stars build` targets, only reachable once
+ * {@link StarsExperimentalConfig.enableNitro} (itself gated on {@link StarsExperimentalConfig.enableVite}) is `true`
+ * — see {@link StarsExperimentalConfig}.
+ */
+interface StarsNitroConfig {
+  /** Additional Nitro options (routeRules, runtimeConfig, storage, publicAssets, hooks, etc.).
+   * Use `defineNitroConfig` from `@wolfstar/nitro-server` for upstream option completion.
+   * Stars owns rootDir, serverEntry, output.dir and the reserved virtual entry.
+   */
+  [option: string]: unknown;
+  /**
+   * `'node-server'` (the default, runs locally with plain `node`), `'cloudflare-module'`, `'aws-lambda'`,
+   * `'vercel'`, `'netlify'`, `'bun'`, `'deno-deploy'`, and more — see Nitro's own preset list.
+   * @default 'node-server'
+   */
+  preset?: string;
+}
+/**
+ * Opt-in flags for work that is still landing, in the shape Nuxt's own `experimental` block has: every flag is a
+ * boolean, defaults to `false`, and is documented with what it changes and what it still needs. A flag stays here
+ * until the behaviour it guards is the default (or is dropped), so enabling one is a statement that breakage is
+ * acceptable in exchange for the feature.
+ *
+ * `enableExternalVite`, `enableNitro` and `nitro` build on `enableVite` (and `nitro` on `enableNitro` too): the type
+ * only accepts them once their prerequisite is `true`, so turning one on without the other is a type error here
+ * instead of a diagnostic at load time.
+ */
+type StarsExperimentalConfig = {
+  enableVite?: false;
+  enableExternalVite?: false;
+  enableNitro?: false;
+} | {
+  /**
+   * Uses Vite as the project's build tool, in place of `tsdown`. `build.tool` may then be set to `'vite'`
+   * (and `'auto'` detects a `vite.config.*`); the bot keeps calling `client.listen()` and running as a
+   * plain `node:http` process, restarted on every change — this only swaps the bundler.
+   */
+  enableVite: true;
+  /**
+   * Runs the bot through Vite itself, the way `nuxt dev` runs on Vite's own dev server: instead of
+   * building then restarting a child `node` process on every change, `stars dev` loads the entry through
+   * Vite's SSR module graph and serves it — through `Client#fetch` — from one long-lived process,
+   * invalidating and re-evaluating just the entry's module graph on a change instead of restarting.
+   *
+   * With this on, the entry's default export must be the `Client` instance (already `load()`ed, not
+   * `listen()`ed) rather than a script that calls `client.listen()` itself — `stars dev` owns the socket.
+   * @default false
+   */
+  enableExternalVite?: boolean;
+  enableNitro?: false;
+} | {
+  enableVite: true;
+  enableExternalVite?: boolean;
+  /**
+   * Builds the bot through [Nitro](https://nitro.build) instead of a `node:http` server, so `stars build`
+   * produces a server deployable to any of Nitro's presets (`node-server` locally, `cloudflare-module`,
+   * `aws-lambda`, `vercel`, `netlify`, `bun`, `deno-deploy`, and more). Nitro v3 is itself a Vite plugin, so
+   * this builds through the project's own `vite.config.*`/{@link StarsConfig.vite} the same way `build.tool:
+   * 'vite'` does, with a generated server entry that wraps the entry's default export (the `Client`
+   * instance, already `load()`ed rather than `listen()`ed — `stars build`/`stars dev` own the socket) in a
+   * call to `Client#fetch` — no per-preset adapter to maintain.
+   *
+   * Output goes to `.output/` (Nitro's own convention) instead of `build.outDir`. `stars dev` rebuilds and
+   * restarts on every change, the same as the other build tools.
+   */
+  enableNitro: true;
+  /** Nitro-specific options, reachable only with `enableNitro: true`. */
+  nitro?: StarsNitroConfig;
+};
+interface StarsConfig {
+  /**
+   * The project root. Relative paths are resolved from the configuration file.
+   * @default dirname(configFile)
+   */
+  root?: string;
+  /**
+   * The source entry point of the bot, relative to {@link StarsConfig.root}.
+   * @default the first of 'src/main.ts', 'src/main.js', 'src/index.ts', 'src/index.js' that exists
+   */
+  entry?: string;
+  build?: StarsBuildConfig;
+  dev?: StarsDevConfig;
+  codegen?: StarsCodegenConfig;
+  /**
+   * Nuxt-style auto imports of the framework's exports and the project's own modules.
+   * `false` disables them, `true` forces them on (requires the `tsdown` build tool). On by default with
+   * `future.compatibilityVersion: 4`.
+   */
+  imports?: StarsImportsConfig | boolean;
+  /** Opt-in flags for behaviour that is still landing. */
+  experimental?: StarsExperimentalConfig;
+  /** Build-default compatibility. Omit for version 4; set version 3 only while migrating a standalone tsdown config. */
+  future?: StarsFutureConfig;
+  /**
+   * Raw options merged into `vite.config.*`, the way `vite: {}` in a Nuxt config is merged into Nuxt's own Vite
+   * config. Only used with `build.tool: 'vite'` (see `experimental.enableVite`).
+   */
+  vite?: StarsViteConfig;
+  /**
+   * The project's `tsdown` build. Replaces `tsdown.config.*` with `future.compatibilityVersion: 4`, and is merged
+   * over it with `3`. Only used with `build.tool: 'tsdown'`.
+   */
+  tsdown?: StarsTsdownConfig;
+}
+//#endregion
+//#region src/config.d.ts
+/**
+ * Typed helper for `stars.config.{ts,mts,cts,js,mjs,cjs}` files.
+ *
+ * @example
+ * ```ts
+ * import { defineConfig } from '@wolfstar/http-framework/config';
+ *
+ * export default defineConfig({
+ * 	entry: 'src/main.ts',
+ * 	build: { tool: 'tsdown' }
+ * });
+ * ```
+ */
+export declare function defineConfig(config: StarsConfig): StarsConfig;
+//#endregion
+export type { StarsBuildConfig, StarsBuildTool, StarsCodegenConfig, StarsCompatibilityVersion, StarsConfig, StarsDevConfig, StarsExperimentalConfig, StarsFutureConfig, StarsI18nCodegenConfig, StarsImportsConfig, StarsNitroConfig, StarsTsdownConfig, StarsTunnelConfig, StarsTypecheckConfig, StarsTypechecker, StarsViteConfig };
+//# sourceMappingURL=config.d.ts.map

package/dist/esm/config.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"config.d.ts","names":[],"sources":["../../src/types/config.ts","../../src/config.ts"],"mappings":";;;;;;;;;;;KAUY;UAEK;;;;;EAKhB,OAAO;;;;;EAKP;;;;;EAKA;;;;;;;KAQW,kBAAkB;;;;;;;;;;;;;;UAeb;;EAEhB,qCAAqC;;EAErC,8DAA8D;;EAE9D;EACA;;;;;;EAMA;;EAEA;EACA,QAAQ;EACR,SAAS;EACT;EACA;EACA,OAAO;;EAEP;;EAEA;EACA;;EAEA,gBAAgB;;EAEhB;EACA;EACA;EACA,QAAQ;GACP;;;;;;KAOU;;;;;UAMK;;;;;;;;;;;;;;;;EAgBhB,uBAAuB;;;;;;;;;;KAWZ;UAEK;;;;;EAKhB;;;;;EAKA,UAAU;;UAGM;;;;EAIhB;;;;;;;;EAQA;;;;;EAKA;;UAGgB;;EAEhB;;;;;;EAMA;;;;;EAKA;;;;;EAKA;;;;EAIA,MAAM;;;;;EAKN;;;;;EAKA;;;;;;;;;;EAUA;;;;;EAKA;;;;;EAKA;;;;;;;EAOA,sBAAsB;;;;;;;;EAQtB,4BAA4B;;;;;;EAM5B;;UAGgB;;;;;EAKhB;;;;;EAKA;;UAGgB;;;;;EAKhB,OAAO;;UAGS;;;;;;EAMhB;;;;;;EAMA;;;;;EAKA;;;;;EAKA;;;;;;EAMA;;;;;;;UAQgB;;;;;GAKf;;;;;;EAMD;;;;;;;;;;;;KAaW;EACP;EAAoB;EAA4B;;;;;;;EAOlD;;;;;;;;;;;EAWA;EACA;;EAGA;EACA;;;;;;;;;;;;;EAaA;;EAEA,QAAQ;;UAGM;;;;;EAKhB;;;;;EAKA;EACA,QAAQ;EACR,MAAM;EACN,UAAU;;;;;;EAMV,UAAU;;EAEV,eAAe;;EAEf,SAAS;;;;;EAKT,OAAO;;;;;EAKP,SAAS;;;;;;;;;;;;;;;;;wBCrXM,aAAa,QAAQ,cAAc"}