tsdown 0.22.3 → 0.22.5

package/dist/types-n62VBdgE.d.mts

@@ -0,0 +1,1427 @@
+import { a as Awaitable, i as Arrayable, n as Logger, o as MarkPartial, s as Overwrite, t as LogLevel } from "./logger-Dewu9aCG.mjs";
+import { BuildOptions, ChecksOptions, ExternalOption, InputOptions, InternalModuleFormat, MinifyOptions, ModuleFormat, ModuleTypes, OutputAsset, OutputChunk, OutputOptions, Plugin, RolldownPlugin, TreeshakingOptions } from "rolldown";
+import { Hookable } from "hookable";
+import { Buffer } from "node:buffer";
+import { StartOptions } from "@vitejs/devtools/cli-commands";
+import { ExeExtensionOptions } from "@tsdown/exe";
+import { CheckPackageOptions } from "@arethetypeswrong/core";
+import { Options } from "publint";
+import { CssOptions } from "@tsdown/css";
+import { Options as Options$1 } from "rolldown-plugin-dts";
+import { Options as UnusedOptions } from "unplugin-unused";
+//#region src/features/copy.d.ts
+interface CopyEntry {
+  /**
+   * Source path or glob pattern.
+   */
+  from: string | string[];
+  /**
+   * Destination path.
+   * If not specified, defaults to the output directory ("outDir").
+   */
+  to?: string;
+  /**
+   * Whether to flatten the copied files (not preserving directory structure).
+   *
+   * @default true
+   */
+  flatten?: boolean;
+  /**
+   * Output copied items to console.
+   * @default false
+   */
+  verbose?: boolean;
+  /**
+   * Change destination file or folder name.
+   */
+  rename?: string | ((name: string, extension: string, fullPath: string) => string);
+}
+type CopyOptions = Arrayable<string | CopyEntry>;
+type CopyOptionsFn = (options: ResolvedConfig) => Awaitable<CopyOptions>;
+//#endregion
+//#region src/utils/chunks.d.ts
+type RolldownChunk = (OutputChunk | OutputAsset) & {
+  outDir: string;
+};
+type ChunksByFormat = Partial<Record<NormalizedFormat, RolldownChunk[]>>;
+interface TsdownBundle extends AsyncDisposable {
+  chunks: RolldownChunk[];
+  config: ResolvedConfig;
+  inlinedDeps: Map<string, Set<string>>;
+}
+//#endregion
+//#region src/features/deps.d.ts
+type NoExternalFn = (id: string, importer: string | undefined) => boolean | null | undefined | void;
+interface DepsConfig {
+  /**
+   * Mark dependencies as external (not bundled).
+   * Accepts strings, regular expressions, or Rolldown's
+   * {@linkcode ExternalOption}.
+   */
+  neverBundle?: ExternalOption;
+  /**
+   * Force dependencies to be bundled, even if they are in `dependencies`, `peerDependencies`, or `optionalDependencies`.
+   */
+  alwaysBundle?: Arrayable<string | RegExp> | NoExternalFn;
+  /**
+   * Whitelist of dependencies allowed to be bundled from `node_modules`.
+   * Throws an error if any unlisted dependency is bundled.
+   *
+   * - `undefined` (default): Show warnings for bundled dependencies.
+   * - `false`: Suppress all warnings about bundled dependencies.
+   *
+   * Note: Be sure to include all required sub-dependencies as well.
+   */
+  onlyBundle?: Arrayable<string | RegExp> | false;
+  /**
+   * @deprecated Use {@linkcode onlyBundle} instead.
+   */
+  onlyAllowBundle?: Arrayable<string | RegExp> | false;
+  /**
+   * Skip bundling all `node_modules` dependencies.
+   *
+   * **Note:** This option cannot be used together with {@linkcode alwaysBundle}.
+   *
+   * @default false
+   */
+  skipNodeModulesBundle?: boolean;
+  /**
+   * Override dependency bundling options for declaration file generation.
+   */
+  dts?: Pick<DepsConfig, "alwaysBundle" | "neverBundle">;
+}
+interface ResolvedDepsConfig {
+  neverBundle?: ExternalOption;
+  alwaysBundle?: NoExternalFn;
+  onlyBundle?: Array<string | RegExp> | false;
+  skipNodeModulesBundle: boolean;
+  /**
+   * Override dependency bundling options for declaration file generation.
+   */
+  dts: Pick<ResolvedDepsConfig, "alwaysBundle" | "neverBundle">;
+}
+declare function DepsPlugin({ pkg, deps: { alwaysBundle: jsAlwaysBundle, onlyBundle, skipNodeModulesBundle, dts }, logger, nameLabel }: ResolvedConfig, tsdownBundle: TsdownBundle): Plugin;
+//#endregion
+//#region src/features/devtools.d.ts
+interface DevtoolsOptions extends NonNullable<InputOptions["devtools"]> {
+  /**
+   * **[experimental]** Enable devtools integration. `@vitejs/devtools` must be installed as a dependency.
+   *
+   * Defaults to true, if `@vitejs/devtools` is installed.
+   */
+  ui?: boolean | Partial<StartOptions>;
+  /**
+   * Clean devtools stale sessions.
+   *
+   * @default true
+   */
+  clean?: boolean;
+}
+//#endregion
+//#region src/features/exe.d.ts
+interface ExeOptions extends ExeExtensionOptions {
+  seaConfig?: Omit<SeaConfig, "main" | "output" | "mainFormat">;
+  /**
+   * Output file name without any suffix or extension.
+   * For example, do not include `.exe`, platform suffixes, or architecture suffixes.
+   */
+  fileName?: string | ((chunk: RolldownChunk) => string);
+  /**
+   * Output directory for executables.
+   * @default 'build'
+   */
+  outDir?: string;
+}
+/**
+ * See also [Node.js SEA Documentation](https://nodejs.org/api/single-executable-applications.html#generating-single-executable-applications-with---build-sea)
+ *
+ * Note some default values are different from Node.js defaults to optimize for typical use cases (e.g. disabling experimental warning, enabling code cache). These can be overridden.
+ */
+interface SeaConfig {
+  main?: string;
+  /**
+   * Optional, if not specified, uses the current Node.js binary
+   */
+  executable?: string;
+  output?: string;
+  /**
+   * @default tsdownConfig.format === 'es' ? 'module' : 'commonjs'
+   */
+  mainFormat?: "commonjs" | "module";
+  /**
+   * @default true
+   */
+  disableExperimentalSEAWarning?: boolean;
+  /**
+   * @default false
+   */
+  useSnapshot?: boolean;
+  /**
+   * @default false
+   */
+  useCodeCache?: boolean;
+  execArgv?: string[];
+  /**
+   * @default 'env'
+   */
+  execArgvExtension?: "none" | "env" | "cli";
+  assets?: Record<string, string>;
+}
+//#endregion
+//#region src/features/hooks.d.ts
+interface BuildContext {
+  options: ResolvedConfig;
+  hooks: Hookable<TsdownHooks>;
+}
+interface RolldownContext {
+  buildOptions: BuildOptions;
+}
+/**
+ * Hooks for tsdown.
+ */
+interface TsdownHooks {
+  /**
+   * Invoked before each tsdown build starts.
+   * Use this hook to perform setup or preparation tasks.
+   */
+  "build:prepare": (ctx: BuildContext) => void | Promise<void>;
+  /**
+   * Invoked before each Rolldown build.
+   * For dual-format builds, this hook is called for each format.
+   * Useful for configuring or modifying the build context before bundling.
+   */
+  "build:before": (ctx: BuildContext & RolldownContext) => void | Promise<void>;
+  /**
+   * Invoked after each tsdown build completes.
+   * Use this hook for cleanup or post-processing tasks.
+   */
+  "build:done": (ctx: BuildContext & {
+    chunks: RolldownChunk[];
+  }) => void | Promise<void>;
+}
+//#endregion
+//#region node_modules/.pnpm/pkg-types@2.3.1/node_modules/pkg-types/dist/index.d.mts
+//#endregion
+//#region src/packagejson/types.d.ts
+interface PackageJson {
+  /**
+   * The name is what your thing is called.
+   * Some rules:
+   * - The name must be less than or equal to 214 characters. This includes the scope for scoped packages.
+   * - The name can’t start with a dot or an underscore.
+   * - New packages must not have uppercase letters in the name.
+   * - The name ends up being part of a URL, an argument on the command line, and a folder name. Therefore, the name can’t contain any non-URL-safe characters.
+   */
+  name?: string;
+  /**
+   * Version must be parseable by `node-semver`, which is bundled with npm as a dependency. (`npm install semver` to use it yourself.)
+   */
+  version?: string;
+  /**
+   * Put a description in it. It’s a string. This helps people discover your package, as it’s listed in `npm search`.
+   */
+  description?: string;
+  /**
+   * Put keywords in it. It’s an array of strings. This helps people discover your package as it’s listed in `npm search`.
+   */
+  keywords?: string[];
+  /**
+   * The url to the project homepage.
+   */
+  homepage?: string;
+  /**
+   * The url to your project’s issue tracker and / or the email address to which issues should be reported. These are helpful for people who encounter issues with your package.
+   */
+  bugs?: string | {
+    url?: string;
+    email?: string;
+  };
+  /**
+   * You should specify a license for your package so that people know how they are permitted to use it, and any restrictions you’re placing on it.
+   */
+  license?: string;
+  /**
+   * Specify the place where your code lives. This is helpful for people who want to contribute. If the git repo is on GitHub, then the `npm docs` command will be able to find you.
+   * For GitHub, GitHub gist, Bitbucket, or GitLab repositories you can use the same shortcut syntax you use for npm install:
+   */
+  repository?: string | {
+    type: string;
+    url: string;
+    /**
+     * If the `package.json` for your package is not in the root directory (for example if it is part of a monorepo), you can specify the directory in which it lives:
+     */
+    directory?: string;
+  };
+  /**
+   * The `scripts` field is a dictionary containing script commands that are run at various times in the lifecycle of your package.
+   */
+  scripts?: PackageJsonScripts;
+  /**
+   * If you set `"private": true` in your package.json, then npm will refuse to publish it.
+   */
+  private?: boolean;
+  /**
+   * The “author” is one person.
+   */
+  author?: PackageJsonPerson;
+  /**
+   * “contributors” is an array of people.
+   */
+  contributors?: PackageJsonPerson[];
+  /**
+   * An object containing a URL that provides up-to-date information
+   * about ways to help fund development of your package,
+   * a string URL, or an array of objects and string URLs
+   */
+  funding?: PackageJsonFunding | PackageJsonFunding[];
+  /**
+   * The optional `files` field is an array of file patterns that describes the entries to be included when your package is installed as a dependency. File patterns follow a similar syntax to `.gitignore`, but reversed: including a file, directory, or glob pattern (`*`, `**\/*`, and such) will make it so that file is included in the tarball when it’s packed. Omitting the field will make it default to `["*"]`, which means it will include all files.
+   */
+  files?: string[];
+  /**
+   * The main field is a module ID that is the primary entry point to your program. That is, if your package is named `foo`, and a user installs it, and then does `require("foo")`, then your main module’s exports object will be returned.
+   * This should be a module ID relative to the root of your package folder.
+   * For most modules, it makes the most sense to have a main script and often not much else.
+   */
+  main?: string;
+  /**
+   * If your module is meant to be used client-side the browser field should be used instead of the main field. This is helpful to hint users that it might rely on primitives that aren’t available in Node.js modules. (e.g. window)
+   */
+  browser?: string | Record<string, string | false>;
+  /**
+   * The `unpkg` field is used to specify the URL to a UMD module for your package. This is used by default in the unpkg.com CDN service.
+   */
+  unpkg?: string;
+  /**
+   * A map of command name to local file name. On install, npm will symlink that file into `prefix/bin` for global installs, or `./node_modules/.bin/` for local installs.
+   */
+  bin?: string | Record<string, string>;
+  /**
+   * Specify either a single file or an array of filenames to put in place for the `man` program to find.
+   */
+  man?: string | string[];
+  /**
+   * Dependencies are specified in a simple object that maps a package name to a version range. The version range is a string which has one or more space-separated descriptors. Dependencies can also be identified with a tarball or git URL.
+   */
+  dependencies?: Record<string, string>;
+  /**
+   * If someone is planning on downloading and using your module in their program, then they probably don’t want or need to download and build the external test or documentation framework that you use.
+   * In this case, it’s best to map these additional items in a `devDependencies` object.
+   */
+  devDependencies?: Record<string, string>;
+  /**
+   * If a dependency can be used, but you would like npm to proceed if it cannot be found or fails to install, then you may put it in the `optionalDependencies` object. This is a map of package name to version or url, just like the `dependencies` object. The difference is that build failures do not cause installation to fail.
+   */
+  optionalDependencies?: Record<string, string>;
+  /**
+   * In some cases, you want to express the compatibility of your package with a host tool or library, while not necessarily doing a `require` of this host. This is usually referred to as a plugin. Notably, your module may be exposing a specific interface, expected and specified by the host documentation.
+   */
+  peerDependencies?: Record<string, string>;
+  /**
+   * TypeScript typings, typically ending by `.d.ts`.
+   */
+  types?: string;
+  /**
+   * This field is synonymous with `types`.
+   */
+  typings?: string;
+  /**
+   * Non-Standard Node.js alternate entry-point to main.
+   * An initial implementation for supporting CJS packages (from main), and use module for ESM modules.
+   */
+  module?: string;
+  /**
+   * Make main entry-point be loaded as an ESM module, support "export" syntax instead of "require"
+   *
+   * Docs:
+   * - https://nodejs.org/docs/latest-v14.x/api/esm.html#esm_package_json_type_field
+   *
+   * @default 'commonjs'
+   * @since Node.js v14
+   */
+  type?: "module" | "commonjs";
+  /**
+   * Alternate and extensible alternative to "main" entry point.
+   *
+   * When using `{type: "module"}`, any ESM module file MUST end with `.mjs` extension.
+   *
+   * Docs:
+   * - https://nodejs.org/docs/latest-v14.x/api/esm.html#esm_exports_sugar
+   *
+   * @since Node.js v12.7
+   */
+  exports?: PackageJsonExports;
+  /**
+   *  Docs:
+   *  - https://nodejs.org/api/packages.html#imports
+   */
+  imports?: Record<string, string | Record<string, string>>;
+  /**
+   * The field is used to define a set of sub-packages (or workspaces) within a monorepo.
+   *
+   * This field is an array of glob patterns or an object with specific configurations for managing
+   * multiple packages in a single repository.
+   */
+  workspaces?: string[] | {
+    /**
+     * Workspace package paths. Glob patterns are supported.
+     */
+    packages?: string[];
+    /**
+     * Packages to block from hoisting to the workspace root.
+     * Uses glob patterns to match module paths in the dependency tree.
+     *
+     * Docs:
+     * - https://classic.yarnpkg.com/blog/2018/02/15/nohoist/
+     */
+    nohoist?: string[];
+  };
+  /**
+   * The field is used to specify different TypeScript declaration files for
+   * different versions of TypeScript, allowing for version-specific type definitions.
+   */
+  typesVersions?: Record<string, Record<string, string[]>>;
+  /**
+   * You can specify which operating systems your module will run on:
+   * ```json
+   * {
+   *   "os": ["darwin", "linux"]
+   * }
+   * ```
+   * You can also block instead of allowing operating systems, just prepend the blocked os with a '!':
+   * ```json
+   * {
+   *   "os": ["!win32"]
+   * }
+   * ```
+   * The host operating system is determined by `process.platform`
+   * It is allowed to both block and allow an item, although there isn't any good reason to do this.
+   */
+  os?: string[];
+  /**
+   * If your code only runs on certain cpu architectures, you can specify which ones.
+   * ```json
+   * {
+   *   "cpu": ["x64", "ia32"]
+   * }
+   * ```
+   * Like the `os` option, you can also block architectures:
+   * ```json
+   * {
+   *   "cpu": ["!arm", "!mips"]
+   * }
+   * ```
+   * The host architecture is determined by `process.arch`
+   */
+  cpu?: string[];
+  /**
+   * This is a set of config values that will be used at publish-time.
+   */
+  publishConfig?: {
+    /**
+     * The registry that will be used if the package is published.
+     */
+    registry?: string;
+    /**
+     * The tag that will be used if the package is published.
+     */
+    tag?: string;
+    /**
+     * The access level that will be used if the package is published.
+     */
+    access?: "public" | "restricted";
+    /**
+     * **pnpm-only**
+     *
+     * By default, for portability reasons, no files except those listed in
+     * the bin field will be marked as executable in the resulting package
+     * archive. The executableFiles field lets you declare additional fields
+     * that must have the executable flag (+x) set even if
+     * they aren't directly accessible through the bin field.
+     */
+    executableFiles?: string[];
+    /**
+     * **pnpm-only**
+     *
+     * You also can use the field `publishConfig.directory` to customize
+     * the published subdirectory relative to the current `package.json`.
+     *
+     * It is expected to have a modified version of the current package in
+     * the specified directory (usually using third party build tools).
+     */
+    directory?: string;
+    /**
+     * **pnpm-only**
+     *
+     * When set to `true`, the project will be symlinked from the
+     * `publishConfig.directory` location during local development.
+     * @default true
+     */
+    linkDirectory?: boolean;
+  } & Pick<PackageJson, "bin" | "main" | "exports" | "types" | "typings" | "module" | "browser" | "unpkg" | "typesVersions" | "os" | "cpu">;
+  /**
+   * See: https://nodejs.org/api/packages.html#packagemanager
+   * This field defines which package manager is expected to be used when working on the current project.
+   * Should be of the format: `<name>@<version>[#hash]`
+   */
+  packageManager?: string;
+  [key: string]: any;
+}
+/**
+ * See: https://docs.npmjs.com/cli/v11/using-npm/scripts#pre--post-scripts
+ */
+type PackageJsonScriptWithPreAndPost<S extends string> = S | `${"pre" | "post"}${S}`;
+/**
+ * See: https://docs.npmjs.com/cli/v11/using-npm/scripts#life-cycle-operation-order
+ */
+type PackageJsonNpmLifeCycleScripts = "dependencies" | "prepublishOnly" | PackageJsonScriptWithPreAndPost<"install" | "pack" | "prepare" | "publish" | "restart" | "start" | "stop" | "test" | "version">;
+/**
+ * See: https://pnpm.io/scripts#lifecycle-scripts
+ */
+type PackageJsonPnpmLifeCycleScripts = "pnpm:devPreinstall";
+type PackageJsonCommonScripts = "build" | "coverage" | "deploy" | "dev" | "format" | "lint" | "preview" | "release" | "typecheck" | "watch";
+type PackageJsonScriptName = PackageJsonCommonScripts | PackageJsonNpmLifeCycleScripts | PackageJsonPnpmLifeCycleScripts | (string & {});
+type PackageJsonScripts = { [P in PackageJsonScriptName]?: string; };
+/**
+ * A “person” is an object with a “name” field and optionally “url” and “email”. Or you can shorten that all into a single string, and npm will parse it for you.
+ */
+type PackageJsonPerson = string | {
+  name: string;
+  email?: string;
+  url?: string;
+};
+type PackageJsonFunding = string | {
+  url: string;
+  type?: string;
+};
+type PackageJsonExportKey = "." | "import" | "require" | "types" | "node" | "browser" | "default" | (string & {});
+type PackageJsonExportsObject = { [P in PackageJsonExportKey]?: string | PackageJsonExportsObject | Array<string | PackageJsonExportsObject>; };
+type PackageJsonExports = string | PackageJsonExportsObject | Array<string | PackageJsonExportsObject>;
+//#endregion
+//#region src/utils/package.d.ts
+interface PackageJsonWithPath extends PackageJson {
+  packageJsonPath: string;
+}
+type PackageType = "module" | "commonjs" | undefined;
+//#endregion
+//#region src/features/output.d.ts
+interface OutExtensionContext {
+  options: InputOptions;
+  format: NormalizedFormat;
+  /**
+   * `"type"` field in project's `package.json`.
+   */
+  pkgType?: PackageType;
+}
+interface OutExtensionObject {
+  js?: string;
+  dts?: string;
+}
+type OutExtensionFactory = (context: OutExtensionContext) => OutExtensionObject | undefined;
+interface ChunkAddonObject {
+  js?: string;
+  css?: string;
+  dts?: string;
+}
+type ChunkAddonFunction = (ctx: {
+  format: Format;
+  fileName: string;
+}) => ChunkAddonObject | string | undefined;
+type ChunkAddon = ChunkAddonObject | ChunkAddonFunction | string;
+//#endregion
+//#region src/features/pkg/attw.d.ts
+interface AttwOptions extends CheckPackageOptions {
+  module?: typeof import("@arethetypeswrong/core");
+  /**
+   * Profiles select a set of resolution modes to require/ignore. All are evaluated but failures outside
+   * of those required are ignored.
+   *
+   * The available profiles are:
+   * - `strict`: requires all resolutions
+   * - `node16`: ignores node10 resolution failures
+   * - `esm-only`: ignores CJS resolution failures
+   *
+   * @default 'strict'
+   */
+  profile?: "strict" | "node16" | "esm-only";
+  /**
+   * The level of the check.
+   *
+   * The available levels are:
+   * - `error`: fails the build
+   * - `warn`: warns the build
+   *
+   * @default 'warn'
+   */
+  level?: "error" | "warn";
+  /**
+   * List of problem types to ignore by rule name.
+   *
+   * The available values are:
+   * - `no-resolution`
+   * - `untyped-resolution`
+   * - `false-cjs`
+   * - `false-esm`
+   * - `cjs-resolves-to-esm`
+   * - `fallback-condition`
+   * - `cjs-only-exports-default`
+   * - `named-exports`
+   * - `false-export-default`
+   * - `missing-export-equals`
+   * - `unexpected-module-syntax`
+   * - `internal-resolution-error`
+   *
+   * @example
+   * ```ts
+   * ignoreRules: ['no-resolution', 'false-cjs']
+   * ```
+   *
+   * @default []
+   *
+   * @uniqueItems
+   */
+  ignoreRules?: ("no-resolution" | "untyped-resolution" | "false-cjs" | "false-esm" | "cjs-resolves-to-esm" | "fallback-condition" | "cjs-only-exports-default" | "named-exports" | "false-export-default" | "missing-export-equals" | "unexpected-module-syntax" | "internal-resolution-error" | (string & {}))[];
+}
+//#endregion
+//#region src/features/pkg/exports.d.ts
+interface ExportsOptions {
+  /**
+   * Generate exports that link to source code during development.
+   * - `string`: add as a custom condition.
+   * - `true`: all conditions point to source files, and add `dist` exports to `publishConfig`.
+   */
+  devExports?: boolean | string;
+  /**
+   * Generate `exports` for `package.json` file.
+   *
+   * @example
+   * ```json
+   * {
+   *   "exports": {
+   *      ".": {
+   *         "types": "./dist/index.d.mts",
+   *         "import": "./dist/index.mjs"
+   *      },
+   *     "./package.json": "./package.json"
+   *   }
+   * }
+   * ```
+   *
+   * @default true
+   */
+  packageJson?: boolean;
+  /**
+   * Generate `exports` for all files.
+   *
+   * @example
+   * ```json
+   * {
+   *   "exports": {
+   *    "./*": "./*"
+   *   }
+   * }
+   * ```
+   *
+   * @default false
+   */
+  all?: boolean;
+  /**
+   * Specifies file patterns (as glob patterns or regular expressions) to exclude from package exports.
+   * Use this to prevent certain files from being included in the exported package, such as test files, binaries, or internal utilities.
+   *
+   * **Note:** Do not include file extensions, and paths should be relative to the dist directory.
+   *
+   * @example
+   * ```ts
+   * exclude: ['cli', '**\/*.test', /internal/]
+   * ```
+   */
+  exclude?: (RegExp | string)[];
+  /**
+   * Generate legacy fields (`main` and `module`) for older Node.js and bundlers
+   * that do not support package `exports` field.
+   *
+   * Defaults to false, if only ESM builds are included, true otherwise.
+   *
+   * @see {@link https://github.com/publint/publint/issues/24}
+   */
+  legacy?: boolean;
+  /**
+   * Specifies custom exports to add to the package exports in addition to the ones generated by tsdown.
+   * Use this to add additional exports in the exported package, such as workers or assets.
+   *
+   * @example
+   * ```ts
+   * customExports(exports) {
+   *   exports['./worker.js'] = './dist/worker.js';
+   *   return exports;
+   * }
+   * ```
+   *
+   * @example
+   * ```jsonc
+   * {
+   *   "customExports": {
+   *     "./worker.js": {
+   *       "types": "./dist/worker.d.ts",
+   *       "default": "./dist/worker.js"
+   *     }
+   *   }
+   * }
+   * ```
+   */
+  customExports?: Record<string, any> | ((exports: Record<string, any>, context: {
+    pkg: PackageJson;
+    chunks: ChunksByFormat;
+    isPublish: boolean;
+  }) => Awaitable<Record<string, any>>);
+  /**
+   * Generate `inlinedDependencies` field in `package.json`.
+   * Lists dependencies that are physically inlined into the bundle with their exact versions.
+   *
+   * @default true
+   * @see {@link https://github.com/e18e/ecosystem-issues/issues/237}
+   */
+  inlinedDependencies?: boolean;
+  /**
+   * Add file extensions to subpath export keys.
+   *
+   * When enabled, all subpath exports (except the root `"."`) will include
+   * a `.js` extension in the key (e.g., `"./utils.js"` instead of `"./utils"`).
+   *
+   * This follows the Node.js recommendation for subpath exports:
+   * @see {@link https://nodejs.org/api/packages.html#extensions-in-subpaths}
+   *
+   * @default false
+   */
+  extensions?: boolean;
+  /**
+   * Generate the `bin` field in `package.json` for CLI executables.
+   *
+   * Behavior depends on the value:
+   *
+   * - *Unset* (default): Soft auto-detect. Scans entry chunks for shebangs
+   *   (e.g. `#!/usr/bin/env node`). If exactly one is found, it is used as
+   *   the bin entry. If multiple are found, a warning is shown and no `bin`
+   *   field is written. If none are found, nothing happens silently.
+   * - `true`: Strict auto-detect. Same as the default, but throws if
+   *   multiple shebang entries are found, and warns if none are found.
+   *   Use this when your package is known to ship a CLI and you want to
+   *   fail fast on misconfiguration.
+   * - `false`: Disable bin generation entirely, even if shebangs are
+   *   present.
+   * - `string`: Use the given source file path (relative to `cwd`) as the
+   *   CLI entry. The command name is derived from the package name without
+   *   its scope. Warns if the source file does not contain a shebang.
+   * - `Record<string, string>`: Explicitly map command names to source file
+   *   paths (relative to `cwd`). Warns for each source file that does not
+   *   contain a shebang.
+   *
+   * When {@link ExportsOptions.devExports} is enabled, the `bin` field in
+   * `package.json` points to source files during local development, while
+   * `publishConfig.bin` points to built output paths for publishing.
+   *
+   * @example
+   * <caption>Auto-detect a CLI entry from a shebang</caption>
+   *
+   * ```ts
+   * {
+   *   bin: true
+   * }
+   * ```
+   *
+   * @example
+   * <caption>Single CLI command with an explicit source entry</caption>
+   *
+   * ```ts
+   * {
+   *   bin: './src/cli.ts'
+   * }
+   * ```
+   *
+   * @example
+   * <caption>Multiple named CLI commands</caption>
+   *
+   * ```ts
+   * {
+   *   bin: {
+   *     tool: './src/cli.ts',
+   *     serve: './src/cli-extra.ts',
+   *   },
+   * }
+   * ```
+   *
+   * @see {@link https://docs.npmjs.com/cli/v11/configuring-npm/package-json#bin | npm documentation for the `bin` field}
+   */
+  bin?: boolean | string | Record<string, string>;
+}
+//#endregion
+//#region src/features/pkg/publint.d.ts
+interface PublintOptions extends Omit<Options, "pack" | "pkgDir"> {
+  module?: [typeof import("publint"), typeof import("publint/utils")];
+}
+//#endregion
+//#region src/features/plugin.d.ts
+/**
+ * A tsdown-aware plugin. Extends Rolldown's {@linkcode Plugin} with
+ * tsdown-specific lifecycle hooks.
+ *
+ * Plugins that only use Rolldown's own lifecycle continue to work unchanged;
+ * tsdown detects these optional methods via runtime duck-typing.
+ */
+interface TsdownPlugin<A = any> extends Plugin<A> {
+  /**
+   * Modify tsdown's user config before it is resolved. Analogous to Vite's
+   * [`config`](https://vite.dev/guide/api-plugin.html#config) hook.
+   *
+   * The hook may mutate {@linkcode config} in place, or return a partial
+   * {@linkcode UserConfig} that will be deep-merged into the current config.
+   * Array fields are replaced (not concatenated) during merging — to append
+   * plugins, mutate {@linkcode UserConfig.plugins | config.plugins} in place.
+   *
+   * The second argument is the original {@linkcode InlineConfig} passed to
+   * {@linkcode build | build()} (typically the CLI flags), useful for
+   * distinguishing values that came from the command line vs. the config file.
+   *
+   * Plugins injected via {@linkcode UserConfig.fromVite | fromVite} do not
+   * receive this hook, because they are loaded after the
+   * {@linkcode tsdownConfig} phase. Likewise, new plugins added by another
+   * plugin's {@linkcode tsdownConfig} do not themselves receive this hook
+   * (plugins are snapshotted before dispatch).
+   */
+  tsdownConfig?: (config: UserConfig, inlineConfig: InlineConfig) => Awaitable<UserConfig | void | null>;
+  /**
+   * Called after tsdown has fully resolved the user config. Analogous to
+   * Vite's [`configResolved`](https://vite.dev/guide/api-plugin.html#configresolved)
+   * hook.
+   *
+   * This hook fires once per produced {@linkcode ResolvedConfig} — i.e. once
+   * per output format when {@linkcode UserConfig.format | format} is an array.
+   * Typical usage is to stash the resolved config for later use in
+   * Rolldown hooks. Mutations made to {@linkcode resolvedConfig} here are
+   * not supported.
+   */
+  tsdownConfigResolved?: (resolvedConfig: ResolvedConfig) => Awaitable<void>;
+}
+/**
+ * A tsdown plugin slot — accepts tsdown plugins, any Rolldown plugin form,
+ * `null`/`undefined`/`false`, {@linkcode Promise | promises}, and
+ * nested arrays. Mirrors Rolldown's {@linkcode RolldownPluginOption} but with
+ * {@linkcode TsdownPlugin} as the atom so that tsdown-specific hooks are
+ * type-checked.
+ */
+type TsdownPluginOption<A = any> = Awaitable<TsdownPlugin<A> | RolldownPlugin<A> | {
+  name: string;
+} | undefined | null | void | false | TsdownPluginOption<A>[]>;
+//#endregion
+//#region src/features/report.d.ts
+interface ReportOptions {
+  /**
+   * Enable/disable gzip-compressed size reporting.
+   * Compressing large output files can be slow, so disabling this may increase build performance for large projects.
+   *
+   * @default true
+   */
+  gzip?: boolean;
+  /**
+   * Enable/disable brotli-compressed size reporting.
+   * Compressing large output files can be slow, so disabling this may increase build performance for large projects.
+   *
+   * @default false
+   */
+  brotli?: boolean;
+  /**
+   * Skip reporting compressed size for files larger than this size.
+   * @default 1_000_000 // 1 MB
+   */
+  maxCompressSize?: number;
+}
+declare function ReportPlugin(config: ResolvedConfig, cjsDts?: boolean, isDualFormat?: boolean): Plugin;
+//#endregion
+//#region src/config/types.d.ts
+interface DtsOptions extends Options$1 {
+  /**
+   * When building dual ESM+CJS formats, generate a `.d.cts` re-export stub
+   * instead of running a full second TypeScript compilation pass.
+   *
+   * The stub re-exports everything from the corresponding `.d.mts` file,
+   * ensuring CJS and ESM consumers share the same type declarations. This
+   * eliminates the TypeScript "dual module hazard" where separate `.d.cts`
+   * and `.d.mts` declarations cause `TS2352` ("neither type sufficiently
+   * overlaps") errors when casting between types derived from the same class.
+   *
+   * Only applies when building both `esm` and `cjs` formats simultaneously.
+   *
+   * @remarks
+   * The generated `.d.cts` stub uses a relative path to re-export from the
+   * corresponding `.d.mts` file, so both formats must be emitted to the
+   * **same** `outDir`. Splitting CJS and ESM outputs into separate
+   * format-specific directories (e.g. `dist/cjs` and `dist/esm`) is not
+   * supported with this option, because the re-export path would be invalid.
+   *
+   * @default false
+   */
+  cjsReexport?: boolean;
+}
+type Sourcemap = boolean | "inline" | "hidden";
+type Format = ModuleFormat;
+type NormalizedFormat = InternalModuleFormat;
+/**
+ * Extended input option that supports glob negation patterns.
+ *
+ * When using object form, values can be:
+ * - A single glob pattern string
+ * - An array of glob patterns, including negation patterns (prefixed with `!`)
+ *
+ * @example
+ * ```ts
+ * entry: {
+ *   // Single pattern
+ *   "utils/*": "./src/utils/*.ts",
+ *   // Array with negation pattern to exclude files
+ *   "hooks/*": ["./src/hooks/*.ts", "!./src/hooks/index.ts"],
+ * }
+ * ```
+ */
+type TsdownInputOption = Arrayable<string | Record<string, Arrayable<string>>>;
+interface Workspace {
+  /**
+   * Workspace directories. Glob patterns are supported.
+   * - `auto`: Automatically detect `package.json` files in the workspace.
+   * @default 'auto'
+   */
+  include?: "auto" | (string & {}) | string[];
+  /**
+   * Exclude directories from workspace.
+   * Defaults to all `node_modules`, `dist`, `test`, `tests`, `temp`, and `tmp` directories.
+   *
+   * @default ['**\/node_modules/**', '**\/dist/**', '**\/test?(s)/**', '**\/t?(e)mp/**']
+   */
+  exclude?: Arrayable<string>;
+  /**
+   * Path to the workspace configuration file.
+   */
+  config?: boolean | string;
+}
+type CIOption = "ci-only" | "local-only";
+type WithEnabled<T> = boolean | undefined | CIOption | (T & {
+  /**
+   * @default true
+   */
+  enabled?: boolean | CIOption;
+});
+/**
+ * Options for tsdown.
+ */
+interface UserConfig {
+  /**
+   * Defaults to `'src/index.ts'` if it exists.
+   *
+   * Supports glob patterns with negation to exclude files:
+   * @example
+   * ```ts
+   * entry: {
+   *   "hooks/*": ["./src/hooks/*.ts", "!./src/hooks/index.ts"],
+   * }
+   * ```
+   *
+   * @default { index: 'src/index.ts'}
+   */
+  entry?: TsdownInputOption;
+  /**
+   * Dependency handling options.
+   */
+  deps?: DepsConfig;
+  /**
+   * @deprecated Use {@linkcode DepsConfig.neverBundle | deps.neverBundle} instead.
+   */
+  external?: ExternalOption;
+  /**
+   * @deprecated Use {@linkcode DepsConfig.alwaysBundle | deps.alwaysBundle} instead.
+   */
+  noExternal?: Arrayable<string | RegExp> | NoExternalFn;
+  /**
+   * @deprecated Use {@linkcode DepsConfig.onlyBundle | deps.onlyBundle} instead.
+   */
+  inlineOnly?: Arrayable<string | RegExp> | false;
+  /**
+   * @deprecated Use {@linkcode DepsConfig.skipNodeModulesBundle | deps.skipNodeModulesBundle} instead.
+   * @default false
+   */
+  skipNodeModulesBundle?: boolean;
+  alias?: Record<string, string>;
+  /**
+   * @default true
+   */
+  tsconfig?: string | boolean;
+  /**
+   * Specifies the target runtime platform for the build.
+   *
+   * - `node`: Node.js and compatible runtimes (e.g., Deno, Bun).
+   *   For CJS format, this is always set to `node` and cannot be changed.
+   * - `neutral`: A platform-agnostic target with no specific runtime assumptions.
+   * - `browser`: Web browsers.
+   *
+   * @default 'node'
+   * @see https://tsdown.dev/options/platform
+   */
+  platform?: "node" | "neutral" | "browser";
+  /**
+   * Specifies the compilation target environment(s).
+   *
+   * Determines the JavaScript version or runtime(s) for which the code should be compiled.
+   * If not set, defaults to the value of `engines.node` in your project's `package.json`.
+   * If no `engines.node` field exists, no syntax transformations are applied.
+   *
+   * Accepts a single target (e.g., `'es2020'`, `'node18'`, `'baseline-widely-available'`), an array of targets, or `false` to disable all transformations.
+   *
+   * @see {@link https://tsdown.dev/options/target#supported-targets} for a list of valid targets and more details.
+   *
+   * @example
+   * ```jsonc
+   * // Target a single environment
+   * { "target": "node18" }
+   * ```
+   *
+   * @example
+   * ```jsonc
+   * // Target multiple environments
+   * { "target": ["node18", "es2020"] }
+   * ```
+   *
+   * @example
+   * ```jsonc
+   * // Disable all syntax transformations
+   * { "target": false }
+   * ```
+   */
+  target?: string | string[] | false;
+  /**
+   * Compile-time env variables, which can be accessed via `import.meta.env` or `process.env`.
+   * @example
+   * ```json
+   * {
+   *   "DEBUG": true,
+   *   "NODE_ENV": "production"
+   * }
+   * ```
+   *
+   * @default {}
+   */
+  env?: Record<string, any>;
+  /**
+   * Path to env file providing compile-time env variables.
+   * @example
+   * `.env`, `.env.production`, etc.
+   */
+  envFile?: string;
+  /**
+   * When loading env variables from `envFile`, only include variables with these prefixes.
+   * @default 'TSDOWN_'
+   */
+  envPrefix?: string | string[];
+  define?: Record<string, string>;
+  /**
+   * @default false
+   */
+  shims?: boolean;
+  /**
+   * Configure tree shaking options.
+   * @see {@link https://rolldown.rs/options/treeshake} for more details.
+   * @default true
+   */
+  treeshake?: boolean | TreeshakingOptions;
+  /**
+   * Sets how input files are processed.
+   * For example, use 'js' to treat files as JavaScript or 'base64' for images.
+   * Lets you import or require files like images or fonts.
+   * @example
+   * ```json
+   * { ".jpg": "asset", ".png": "base64" }
+   * ```
+   */
+  loader?: ModuleTypes;
+  /**
+   * Remove the `node:` prefix from built-in Node.js module imports.
+   * When enabled, rewrites import sources like `node:fs` to `fs`.
+   *
+   * @default false
+   * @deprecated Use {@linkcode nodeProtocol | nodeProtocol: 'strip'} instead.
+   *
+   * @example
+   * <caption>`removeNodeProtocol: true` — remove the `node:` prefix</caption>
+   *
+   * ```ts
+   * // Input
+   * import 'node:fs'
+   *
+   * // Output
+   * import 'fs'
+   * ```
+   */
+  removeNodeProtocol?: boolean;
+  /**
+   * Control whether built-in Node.js module imports use the `node:` protocol.
+   *
+   * - `true`: Add the `node:` prefix to built-in module imports.
+   * - `'strip'`: Remove the `node:` prefix from built-in module imports.
+   * - `false`: Do not transform built-in module imports.
+   *
+   * @default false
+   *
+   * @example
+   * <caption>`nodeProtocol: true` — add the `node:` prefix</caption>
+   *
+   * ```ts
+   * // Input
+   * import 'fs'
+   *
+   * // Output
+   * import 'node:fs'
+   * ```
+   *
+   * @example
+   * <caption>`nodeProtocol: 'strip'` — remove the `node:` prefix</caption>
+   *
+   * ```ts
+   * // Input
+   * import 'node:fs'
+   *
+   * // Output
+   * import 'fs'
+   * ```
+   *
+   * @example
+   * <caption>`nodeProtocol: false` — do not transform imports</caption>
+   *
+   * ```ts
+   * // Input
+   * import 'node:fs'
+   *
+   * // Output
+   * import 'node:fs'
+   * ```
+   */
+  nodeProtocol?: "strip" | boolean;
+  /**
+   * Controls which warnings are emitted during the build process. Each option can be set to `true` (emit warning) or `false` (suppress warning).
+   */
+  checks?: ChecksOptions & {
+    /**
+     * If the config includes the `cjs` format and
+     * one of its target >= node 20.19.0 / 22.12.0,
+     * warn the user about the deprecation of CommonJS.
+     *
+     * @default true
+     */
+    legacyCjs?: boolean;
+  };
+  plugins?: TsdownPluginOption;
+  /**
+   * Use with caution; ensure you understand the implications.
+   */
+  inputOptions?: InputOptions | ((options: InputOptions, format: NormalizedFormat, context: {
+    cjsDts: boolean;
+  }) => Awaitable<InputOptions | void | null>);
+  /**
+   * Output format(s). Available formats are
+   * - `esm`: ESM
+   * - `cjs`: CommonJS
+   * - `iife`: IIFE
+   * - `umd`: UMD
+   *
+   * @default 'esm'
+   */
+  format?: Format | Format[] | Partial<Record<Format, Partial<ResolvedConfig>>>;
+  globalName?: string;
+  /**
+   * @default 'dist'
+   */
+  outDir?: string;
+  /**
+   * Whether to write the files to disk.
+   * This option is incompatible with watch mode.
+   * @default true
+   */
+  write?: boolean;
+  /**
+   * Whether to generate source map files.
+   *
+   * Note that this option will always be `true` if you have
+   * {@link https://www.typescriptlang.org/tsconfig/#declarationMap | `declarationMap`}
+   * option enabled in your `tsconfig.json`.
+   *
+   * @default false
+   */
+  sourcemap?: Sourcemap;
+  /**
+   * Clean directories before build.
+   *
+   * Default to output directory.
+   * @default true
+   */
+  clean?: boolean | string[];
+  /**
+   * @default false
+   */
+  minify?: boolean | "dce-only" | MinifyOptions;
+  footer?: ChunkAddon;
+  banner?: ChunkAddon;
+  /**
+   * Determines whether `unbundle` is enabled.
+   * When set to `true`, the output files will mirror the input file structure.
+   * @default false
+   */
+  unbundle?: boolean;
+  /**
+   * Specifies the root directory of input files, similar to TypeScript's `rootDir`.
+   * This determines the output directory structure.
+   *
+   * By default, the root is computed as the common base directory of all entry files.
+   *
+   * @see https://www.typescriptlang.org/tsconfig/#rootDir
+   */
+  root?: string;
+  /**
+   * @deprecated Use {@linkcode unbundle} instead.
+   * @default true
+   */
+  bundle?: boolean;
+  /**
+   * Use a fixed extension for output files.
+   * The extension will always be `.cjs` or `.mjs`.
+   * Otherwise, it will depend on the package type.
+   *
+   * Defaults to `true` if {@linkcode platform} is set to `node`,
+   * `false` otherwise.
+   *
+   * @default platform === 'node'
+   */
+  fixedExtension?: boolean;
+  /**
+   * Custom extensions for output files.
+   * {@linkcode fixedExtension} will be overridden by this option.
+   */
+  outExtensions?: OutExtensionFactory;
+  /**
+   * @deprecated Use {@linkcode outExtensions} instead.
+   */
+  outExtension?: OutExtensionFactory;
+  /**
+   * If enabled, appends hash to chunk filenames.
+   * @default true
+   */
+  hash?: boolean;
+  /**
+   * @default true
+   */
+  cjsDefault?: boolean;
+  /**
+   * Use with caution; ensure you understand the implications.
+   */
+  outputOptions?: OutputOptions | ((options: OutputOptions, format: NormalizedFormat, context: {
+    cjsDts: boolean;
+  }) => Awaitable<OutputOptions | void | null>);
+  /**
+   * The working directory of the config file.
+   * - Defaults to {@linkcode process.cwd | process.cwd()} for root config.
+   * - Defaults to the package directory for {@linkcode workspace} config.
+   *
+   * @default process.cwd()
+   */
+  cwd?: string;
+  /**
+   * The name to show in CLI output. This is useful for monorepos or workspaces.
+   * When using workspace mode, this option defaults to the package name from package.json.
+   * In non-workspace mode, this option must be set explicitly for the name to show in the CLI output.
+   */
+  name?: string;
+  /**
+   * Log level.
+   * @default 'info'
+   */
+  logLevel?: LogLevel;
+  /**
+   * If true, fails the build on warnings.
+   * @default false
+   */
+  failOnWarn?: boolean | CIOption;
+  /**
+   * Custom logger.
+   */
+  customLogger?: Logger;
+  /**
+   * Reuse config from Vite or Vitest (experimental)
+   * @default false
+   */
+  fromVite?: boolean | "vitest";
+  /**
+   * @default false
+   */
+  watch?: boolean | Arrayable<string>;
+  /**
+   * Files or patterns to not watch while in watch mode.
+   */
+  ignoreWatch?: Arrayable<string | RegExp>;
+  /**
+   * **[experimental]** Enable devtools.
+   *
+   * DevTools is still under development, and this is for early testers only.
+   *
+   * This may slow down the build process significantly.
+   *
+   * @default false
+   */
+  devtools?: WithEnabled<DevtoolsOptions>;
+  /**
+   * You can specify command to be executed after a successful build, specially useful for Watch mode
+   */
+  onSuccess?: string | ((config: ResolvedConfig, signal: AbortSignal) => void | Promise<void>);
+  /**
+   * Enables generation of TypeScript declaration files (`.d.ts`).
+   *
+   * By default, this option is auto-detected based on your project's `package.json`:
+   * - If {@linkcode exe} is enabled, declaration file generation is disabled by default.
+   * - If the `types` field is present, or if the main `exports` contains a `types` entry, declaration file generation is enabled by default.
+   * - Otherwise, declaration file generation is disabled by default.
+   */
+  dts?: WithEnabled<DtsOptions>;
+  /**
+   * Enable unused dependencies check with `unplugin-unused`
+   * Requires `unplugin-unused` to be installed.
+   * @default false
+   */
+  unused?: WithEnabled<UnusedOptions>;
+  /**
+   * Run `publint` after bundling.
+   * Requires `publint` to be installed.
+   * @default false
+   */
+  publint?: WithEnabled<PublintOptions>;
+  /**
+   * Run `arethetypeswrong` after bundling.
+   * Requires `@arethetypeswrong/core` to be installed.
+   *
+   * @default false
+   * @see https://github.com/arethetypeswrong/arethetypeswrong.github.io
+   */
+  attw?: WithEnabled<AttwOptions>;
+  /**
+   * Enable size reporting after bundling.
+   * @default true
+   */
+  report?: WithEnabled<ReportOptions>;
+  /**
+   * `import.meta.glob` support.
+   * @see https://vite.dev/guide/features.html#glob-import
+   * @default true
+   */
+  globImport?: boolean;
+  /**
+   * Generate package exports for `package.json`.
+   *
+   * This will set the `exports` field in `package.json` to point to the
+   * generated files.
+   *
+   * @default false
+   */
+  exports?: WithEnabled<ExportsOptions>;
+  /**
+   * **[experimental]** CSS options.
+   * Requires `@tsdown/css` to be installed.
+   */
+  css?: CssOptions;
+  /**
+   * @deprecated Use {@linkcode CssOptions.inject | css.inject} instead.
+   */
+  injectStyle?: boolean;
+  /**
+   * @alias copy
+   * @deprecated Alias for {@linkcode copy}, will be removed in the future.
+   */
+  publicDir?: CopyOptions | CopyOptionsFn;
+  /**
+   * Copy files to another directory.
+   * @example
+   * ```ts
+   * [
+   *   'src/assets',
+   *   'src/env.d.ts',
+   *   'src/styles/**\/*.css',
+   *   { from: 'src/assets', to: 'dist/assets' },
+   *   { from: 'src/styles/**\/*.css', to: 'dist', flatten: true },
+   * ]
+   * ```
+   */
+  copy?: CopyOptions | CopyOptionsFn;
+  hooks?: Partial<TsdownHooks> | ((hooks: Hookable<TsdownHooks>) => Awaitable<void>);
+  /**
+   * **[experimental]** Bundle as executable using Node.js SEA (Single Executable Applications).
+   *
+   * This will bundle the output into a single executable file using Node.js SEA.
+   * Note that this is only supported on Node.js 25.7.0 and later, and is not supported in Bun or Deno.
+   *
+   * @default false
+   */
+  exe?: WithEnabled<ExeOptions>;
+  /**
+   * **[experimental]** Enable workspace mode.
+   * This allows you to build multiple packages in a monorepo.
+   */
+  workspace?: Workspace | Arrayable<string> | true;
+}
+interface InlineConfig extends UserConfig {
+  /**
+   * Config file path
+   */
+  config?: boolean | string;
+  /**
+   * Config loader to use. It can only be set via CLI or API.
+   * @default 'auto'
+   */
+  configLoader?: "auto" | "native" | "tsx" | "unrun";
+  /**
+   * Filter configs by cwd or name.
+   */
+  filter?: RegExp | Arrayable<string>;
+}
+type UserConfigFn = (inlineConfig: InlineConfig, context: {
+  ci: boolean;
+  rootConfig?: UserConfig;
+}) => Awaitable<Arrayable<UserConfig>>;
+type UserConfigExport = Awaitable<Arrayable<UserConfig> | UserConfigFn>;
+type ResolvedConfig = Overwrite<MarkPartial<Omit<UserConfig, "workspace" | "fromVite" | "publicDir" | "bundle" | "injectStyle" | "removeNodeProtocol" | "outExtension" | "external" | "noExternal" | "inlineOnly" | "skipNodeModulesBundle" | "logLevel" | "failOnWarn" | "customLogger" | "envFile" | "envPrefix">, "globalName" | "inputOptions" | "outputOptions" | "minify" | "define" | "alias" | "onSuccess" | "outExtensions" | "hooks" | "copy" | "loader" | "name" | "banner" | "footer" | "checks" | "css">, {
+  /**
+   * Resolved entry map (after glob expansion)
+   */
+  entry: Record<string, string>;
+  /**
+   * Original entry config before glob resolution (for watch mode re-globbing)
+   */
+  rawEntry?: TsdownInputOption;
+  nameLabel: string | undefined;
+  format: NormalizedFormat;
+  target?: string[];
+  clean: string[];
+  pkg?: PackageJsonWithPath;
+  nodeProtocol: "strip" | boolean;
+  logger: Logger;
+  ignoreWatch: Array<string | RegExp>;
+  deps: ResolvedDepsConfig;
+  /**
+   * Resolved root directory of input files
+   */
+  root: string;
+  configDeps: Set<string>;
+  dts: false | DtsOptions;
+  report: false | ReportOptions;
+  tsconfig: false | string;
+  exports: false | ExportsOptions;
+  devtools: false | DevtoolsOptions;
+  publint: false | PublintOptions;
+  attw: false | AttwOptions;
+  unused: false | UnusedOptions;
+  exe: false | ExeOptions;
+}>;
+//#endregion
+export { PackageType as A, ResolvedDepsConfig as B, ChunkAddon as C, OutExtensionFactory as D, OutExtensionContext as E, SeaConfig as F, CopyOptionsFn as G, TsdownBundle as H, DevtoolsOptions as I, DepsConfig as L, RolldownContext as M, TsdownHooks as N, OutExtensionObject as O, ExeOptions as P, DepsPlugin as R, AttwOptions as S, ChunkAddonObject as T, CopyEntry as U, RolldownChunk as V, CopyOptions as W, ReportPlugin as _, NormalizedFormat as a, PublintOptions as b, TreeshakingOptions as c, UserConfig as d, UserConfigExport as f, ReportOptions as g, Workspace as h, InlineConfig as i, BuildContext as j, PackageJsonWithPath as k, TsdownInputOption as l, WithEnabled as m, DtsOptions as n, ResolvedConfig as o, UserConfigFn as p, Format as r, Sourcemap as s, CIOption as t, UnusedOptions as u, TsdownPlugin as v, ChunkAddonFunction as w, ExportsOptions as x, TsdownPluginOption as y, NoExternalFn as z };