@powerlines/core 0.48.28 → 0.48.30

package/dist/config-BnV_o0Es.d.cts

@@ -0,0 +1,2461 @@
+import { n as EXECUTION_API_METHODS, t as BASE_EXECUTION_API_METHODS } from "./api-DTCbbtSH.cjs";
+import { t as SUPPORTED_COMMANDS } from "./commands-DzGd8pnR.cjs";
+import { i as LOG_CATEGORIES, o as LOG_LEVELS } from "./log-level-BC8g4BBL.cjs";
+import { i as PLUGIN_NON_HOOK_FIELDS } from "./plugin-fhBG7SSQ.cjs";
+import { EnvPaths } from "@stryke/env/get-env-paths";
+import { Format } from "@storm-software/build-tools/types";
+import { StormWorkspaceConfig } from "@storm-software/config/types";
+import { AnyFunction, DeepPartial, DeepReadonly, MaybePromise, NonUndefined, PartialKeys, RequiredKeys } from "@stryke/types/base";
+import { FileReference, FileReferenceInput } from "@stryke/types/configuration";
+import { AssetGlob } from "@stryke/types/file";
+import { ConfigLayer, ResolvedConfig } from "c12";
+import { CompatibilityDateSpec, CompatibilityDates } from "compatx";
+import { PreviewOptions, ResolvedPreviewOptions } from "vite";
+import { PackageJson } from "@stryke/types/package-json";
+import { Jiti } from "jiti";
+import MagicString, { SourceMap } from "magic-string";
+import { ParseResult, ParserOptions } from "oxc-parser";
+import { Range } from "semver";
+import { RequestInfo, Response } from "undici";
+import { Unimport } from "unimport";
+import { ExternalIdResult, HookFilter, StringOrRegExp, TransformResult, UnpluginBuildContext, UnpluginMessage, UnpluginOptions } from "unplugin";
+import { ResolveOptions } from "@stryke/fs/resolve";
+import { ArrayValues } from "@stryke/types/array";
+import { LoadResult } from "rollup";
+import { CompilerOptions, TsConfigJson } from "@stryke/types/tsconfig";
+import ts from "typescript";
+
+//#region src/types/fs.d.ts
+type VirtualFileExtension = "js" | "ts" | "jsx" | "tsx";
+type StoragePreset = "fs" | "virtual";
+/**
+ * Interface defining the methods and properties for a storage adapter.
+ */
+interface StorageAdapter {
+  /**
+   * A name identifying the storage adapter type.
+   */
+  name: string;
+  /**
+   * The storage preset for the adapter.
+   *
+   * @remarks
+   * This can be used as an alternate way to identify the type of storage being used.
+   */
+  preset?: StoragePreset | null;
+  /**
+   * Checks if a key exists in the storage.
+   *
+   * @param key - The key to check for existence.
+   * @returns A promise that resolves to `true` if the key exists, otherwise `false`.
+   */
+  exists: (key: string) => Promise<boolean>;
+  /**
+   * Synchronously checks if a key exists in the storage.
+   *
+   * @param key - The key to check for existence.
+   * @returns Returns `true` if the key exists, otherwise `false`.
+   */
+  existsSync: (key: string) => boolean;
+  /**
+   * Read a value associated with a key from the storage.
+   *
+   * @param key - The key to read the value for.
+   * @returns A promise that resolves to the value if found, otherwise `null`.
+   */
+  get: (key: string) => Promise<string | null>;
+  /**
+   * Synchronously reads the value associated with a key from the storage.
+   *
+   * @param key - The key to read the value for.
+   * @returns The value if found, otherwise `null`.
+   */
+  getSync: (key: string) => string | null;
+  /**
+   * Writes a value to the storage for the given key.
+   *
+   * @param key - The key to associate the value with.
+   * @param value - The value to store.
+   */
+  set: (key: string, value: string) => Promise<void>;
+  /**
+   * Synchronously writes a value to the storage for the given key.
+   *
+   * @param key - The key to associate the value with.
+   * @param value - The value to store.
+   */
+  setSync: (key: string, value: string) => void;
+  /**
+   * Removes a value from the storage.
+   *
+   * @param key - The key whose value should be removed.
+   */
+  remove: (key: string) => Promise<void>;
+  /**
+   * Synchronously removes a value from the storage.
+   *
+   * @param key - The key whose value should be removed.
+   */
+  removeSync: (key: string) => void;
+  /**
+   * Creates a directory at the specified path.
+   *
+   * @param dirPath - The path of the directory to create.
+   */
+  mkdir: (dirPath: string) => Promise<void>;
+  /**
+   * Synchronously creates a directory at the specified path.
+   *
+   * @param dirPath - The path of the directory to create.
+   */
+  mkdirSync: (dirPath: string) => void;
+  /**
+   * Remove all entries from the storage that match the provided base path.
+   *
+   * @param base - The base path or prefix to clear entries from.
+   */
+  clear: (base?: string) => Promise<void>;
+  /**
+   * Synchronously remove all entries from the storage that match the provided base path.
+   *
+   * @param base - The base path or prefix to clear entries from.
+   */
+  clearSync: (base?: string) => void;
+  /**
+   * Lists all keys under the provided base path.
+   *
+   * @param base - The base path or prefix to list keys from.
+   * @returns A promise resolving to the list of keys.
+   */
+  list: (base?: string) => Promise<string[]>;
+  /**
+   * Synchronously lists all keys under the provided base path.
+   *
+   * @param base - The base path or prefix to list keys from.
+   * @returns The list of keys.
+   */
+  listSync: (base?: string) => string[];
+  /**
+   * Checks if the given key is a directory.
+   *
+   * @param key - The key to check.
+   * @returns A promise that resolves to `true` if the key is a directory, otherwise `false`.
+   */
+  isDirectory: (key: string) => Promise<boolean>;
+  /**
+   * Synchronously checks if the given key is a directory.
+   *
+   * @param key - The key to check.
+   * @returns `true` if the key is a directory, otherwise `false`.
+   */
+  isDirectorySync: (key: string) => boolean;
+  /**
+   * Checks if the given key is a file.
+   *
+   * @param key - The key to check.
+   * @returns A promise that resolves to `true` if the key is a file, otherwise `false`.
+   */
+  isFile: (key: string) => Promise<boolean>;
+  /**
+   * Synchronously checks if the given key is a file.
+   *
+   * @param key - The key to check.
+   * @returns `true` if the key is a file, otherwise `false`.
+   */
+  isFileSync: (key: string) => boolean;
+  /**
+   * Releases any resources held by the storage adapter.
+   */
+  dispose: () => MaybePromise<void>;
+}
+/**
+ * A mapping of file paths to storage adapter names and their corresponding {@link StorageAdapter} instances.
+ */
+type StoragePort = Record<string, StorageAdapter>;
+interface VirtualFileMetadata {
+  /**
+   * The identifier for the file data.
+   */
+  id: string;
+  /**
+   * The timestamp of the virtual file.
+   */
+  timestamp: number;
+  /**
+   * The type of the file.
+   *
+   * @remarks
+   * This string represents the purpose/function of the file in the virtual file system. A potential list of variants includes:
+   * - `builtin`: Indicates that the file is a built-in module provided by the system.
+   * - `entry`: Indicates that the file is an entry point for execution.
+   * - `infrastructure`: Indicates that the file is an infrastructure module used by the system during deployments.
+   * - `normal`: Indicates that the file is a standard file without any special role.
+   */
+  type: string;
+  /**
+   * Additional metadata associated with the file.
+   */
+  properties: Record<string, string | undefined>;
+}
+interface VirtualFileData {
+  /**
+   * The identifier for the file data.
+   */
+  id?: string;
+  /**
+   * The contents of the virtual file.
+   */
+  code: string;
+  /**
+   * The type of the file.
+   *
+   * @remarks
+   * This string represents the purpose/function of the file in the virtual file system. A potential list of variants includes:
+   * - `builtin`: Indicates that the file is a built-in module provided by the system.
+   * - `entry`: Indicates that the file is an entry point for execution.
+   * - `infrastructure`: Indicates that the file is an infrastructure module used by the system during deployments.
+   * - `normal`: Indicates that the file is a standard file without any special role.
+   */
+  type?: string;
+  /**
+   * Additional metadata associated with the file.
+   */
+  properties?: Record<string, string | undefined>;
+}
+interface VirtualFile extends Required<VirtualFileData>, VirtualFileMetadata {
+  /**
+   * An additional name for the file.
+   */
+  path: string;
+  /**
+   * The timestamp of the virtual file.
+   */
+  timestamp: number;
+}
+interface WriteOptions {
+  /**
+   * Should the file skip formatting before being written?
+   *
+   * @defaultValue false
+   */
+  skipFormat?: boolean;
+  /**
+   * The storage preset or adapter name for the output file.
+   *
+   * @remarks
+   * If not specified, the output mode will be determined by the provided `output.mode` value.
+   */
+  storage?: StoragePreset | string;
+  /**
+   * Additional metadata for the file.
+   */
+  meta?: Partial<VirtualFileMetadata>;
+}
+type WriteData = string | NodeJS.ArrayBufferView | VirtualFileData;
+interface ResolveOptions$1 extends ResolveOptions {
+  /**
+   * If true, the module is being resolved as an entry point.
+   */
+  isEntry?: boolean;
+  /**
+   * If true, the resolver will skip alias resolution when resolving modules.
+   */
+  skipAlias?: boolean;
+  /**
+   * If true, the resolver will skip using the cache when resolving modules.
+   */
+  skipCache?: boolean;
+  /**
+   * An array of external modules or patterns to exclude from resolution.
+   */
+  external?: (string | RegExp)[];
+  /**
+   * An array of modules or patterns to include in the resolution, even if they are marked as external.
+   */
+  noExternal?: (string | RegExp)[];
+  /**
+   * An array of patterns to match when resolving modules.
+   */
+  skipNodeModulesBundle?: boolean;
+  /**
+   * If true, the resolver will treat the module as a file.
+   */
+  isFile?: boolean;
+}
+interface VirtualFileSystemInterface {
+  /**
+   * The underlying file metadata.
+   */
+  metadata: Readonly<Record<string, VirtualFileMetadata>>;
+  /**
+   * A map of file paths to their module ids.
+   */
+  ids: Readonly<Record<string, string>>;
+  /**
+   * A map of module ids to their file paths.
+   */
+  paths: Readonly<Record<string, string>>;
+  /**
+   * Checks if a file exists in the virtual file system (VFS).
+   *
+   * @param path - The path or id of the file.
+   * @returns `true` if the file exists, otherwise `false`.
+   */
+  exists: (path: string) => Promise<boolean>;
+  /**
+   * Synchronously Checks if a file exists in the virtual file system (VFS).
+   *
+   * @param path - The path or id of the file.
+   * @returns `true` if the file exists, otherwise `false`.
+   */
+  existsSync: (path: string) => boolean;
+  /**
+   * Checks if a file is virtual in the virtual file system (VFS).
+   *
+   * @param path - The path or id of the file.
+   * @param importer - An optional path to the importer module, used for resolving the file path.
+   * @param options - Additional options for resolving the file path.
+   * @returns `true` if the file is virtual, otherwise `false`.
+   */
+  isVirtual: (path: string, importer?: string | undefined, options?: ResolveOptions$1) => boolean;
+  /**
+   * Checks if the given key is a directory.
+   *
+   * @param key - The key to check.
+   * @param importer - An optional path to the importer module, used for resolving the file path.
+   * @param options - Additional options for resolving the file path.
+   * @returns A promise that resolves to `true` if the key is a directory, otherwise `false`.
+   */
+  isDirectory: (key: string, importer?: string | undefined, options?: ResolveOptions$1) => Promise<boolean>;
+  /**
+   * Synchronously checks if the given key is a directory.
+   *
+   * @param key - The key to check.
+   * @param importer - An optional path to the importer module, used for resolving the file path.
+   * @param options - Additional options for resolving the file path.
+   * @returns `true` if the key is a directory, otherwise `false`.
+   */
+  isDirectorySync: (key: string, importer?: string | undefined, options?: ResolveOptions$1) => boolean;
+  /**
+   * Checks if the given key is a file.
+   *
+   * @param key - The key to check.
+   * @param importer - An optional path to the importer module, used for resolving the file path.
+   * @param options - Additional options for resolving the file path.
+   * @returns A promise that resolves to `true` if the key is a file, otherwise `false`.
+   */
+  isFile: (key: string, importer?: string | undefined, options?: ResolveOptions$1) => Promise<boolean>;
+  /**
+   * Synchronously checks if the given key is a file.
+   *
+   * @param key - The key to check.
+   * @param importer - An optional path to the importer module, used for resolving the file path.
+   * @param options - Additional options for resolving the file path.
+   * @returns `true` if the key is a file, otherwise `false`.
+   */
+  isFileSync: (key: string, importer?: string | undefined, options?: ResolveOptions$1) => boolean;
+  /**
+   * Checks if a file Id must be resolved by the virtual file system (VFS).
+   *
+   * @remarks
+   * Examples of file Ids that would be considered virtual include:
+   * - Ids that start with the framework specific prefix (e.g. `powerlines:`)
+   * - Ids that match a configured alias for virtual modules (returned true from {@link VirtualFileSystemInterface.isVirtual})
+   *
+   * @param path - The path or id of the file.
+   * @param importer - An optional path to the importer module, used for resolving the file path.
+   * @param options - Additional options for resolving the file path.
+   * @returns `true` if the file is virtual, otherwise `false`.
+   */
+  isResolvableId: (path: string, importer?: string | undefined, options?: ResolveOptions$1) => boolean;
+  /**
+   * Checks if a given module ID is an alias.
+   *
+   * @remarks
+   * This function can be used to determine if a module ID matches any configured aliases.
+   *
+   * @param id - The module ID to check.
+   * @returns A boolean indicating whether the module ID is an alias.
+   */
+  isAlias: (id: string) => boolean;
+  /**
+   * Checks if a given module ID is a tsconfig path.
+   *
+   * @remarks
+   * This function can be used to determine if a module ID matches any configured tsconfig paths.
+   *
+   * @param id - The module ID to check.
+   * @returns A boolean indicating whether the module ID is a tsconfig path.
+   */
+  isTsconfigPath: (id: string) => boolean;
+  /**
+   * Gets the metadata of a file in the virtual file system (VFS).
+   *
+   * @param path - The path or id of the file.
+   * @returns The metadata of the file if it exists, otherwise undefined.
+   */
+  getMetadata: (path: string) => VirtualFileMetadata | undefined;
+  /**
+   * Lists files in a given path.
+   *
+   * @param path - The path to list files from.
+   * @returns An array of file names in the specified path.
+   */
+  listSync: (path: string) => string[];
+  /**
+   * Lists files in a given path.
+   *
+   * @param path - The path to list files from.
+   * @returns An array of file names in the specified path.
+   */
+  list: (path: string) => Promise<string[]>;
+  /**
+   * Removes a file or symbolic link in the virtual file system (VFS).
+   *
+   * @param path - The path to the file to remove.
+   * @returns A promise that resolves when the file is removed.
+   */
+  removeSync: (path: string) => void;
+  /**
+   * Asynchronously removes a file or symbolic link in the virtual file system (VFS).
+   *
+   * @param path - The path to the file to remove.
+   * @returns A promise that resolves when the file is removed.
+   */
+  remove: (path: string) => Promise<void>;
+  /**
+   * Reads a file from the virtual file system (VFS).
+   *
+   * @param path - The path or id of the file.
+   * @returns The contents of the file if it exists, otherwise undefined.
+   */
+  read: (path: string) => Promise<string | undefined>;
+  /**
+   * Reads a file from the virtual file system (VFS).
+   *
+   * @param path - The path or id of the file.
+   */
+  readSync: (path: string) => string | undefined;
+  /**
+   * Writes a file to the virtual file system (VFS).
+   *
+   * @param path - The path to the file.
+   * @param data - The contents of the file.
+   * @param options - Options for writing the file.
+   * @returns A promise that resolves when the file is written.
+   */
+  write: (path: string, data: string, options?: WriteOptions) => Promise<void>;
+  /**
+   * Writes a file to the virtual file system (VFS).
+   *
+   * @param path - The path to the file.
+   * @param data - The contents of the file.
+   * @param options - Options for writing the file.
+   */
+  writeSync: (path: string, data: string, options?: WriteOptions) => void;
+  /**
+   * Creates a directory at the specified path.
+   *
+   * @param dirPath - The path of the directory to create.
+   */
+  mkdir: (dirPath: string) => Promise<void>;
+  /**
+   * Synchronously creates a directory at the specified path.
+   *
+   * @param dirPath - The path of the directory to create.
+   */
+  mkdirSync: (dirPath: string) => void;
+  /**
+   * Moves a file from one path to another in the virtual file system (VFS).
+   *
+   * @param srcPath - The source path to move
+   * @param destPath - The destination path to move to
+   */
+  move: (srcPath: string, destPath: string) => Promise<void>;
+  /**
+   * Synchronously moves a file from one path to another in the virtual file system (VFS).
+   *
+   * @param srcPath - The source path to move
+   * @param destPath - The destination path to move to
+   */
+  moveSync: (srcPath: string, destPath: string) => void;
+  /**
+   * Copies a file from one path to another in the virtual file system (VFS).
+   *
+   * @param srcPath - The source path to copy
+   * @param destPath - The destination path to copy to
+   */
+  copy: (srcPath: string | URL | Omit<AssetGlob, "output">, destPath: string | URL) => Promise<void>;
+  /**
+   * Synchronously copies a file from one path to another in the virtual file system (VFS).
+   *
+   * @param srcPath - The source path to copy
+   * @param destPath - The destination path to copy to
+   */
+  copySync: (srcPath: string | URL | Omit<AssetGlob, "output">, destPath: string | URL) => void;
+  /**
+   * Glob files in the virtual file system (VFS) based on the provided pattern(s).
+   *
+   * @param pattern - A pattern (or multiple patterns) to use to determine the file paths to return
+   * @returns An array of file paths matching the provided pattern(s)
+   */
+  glob: (patterns: string | Omit<AssetGlob, "output"> | (string | Omit<AssetGlob, "output">)[]) => Promise<string[]>;
+  /**
+   * Synchronously glob files in the virtual file system (VFS) based on the provided pattern(s).
+   *
+   * @param pattern - A pattern (or multiple patterns) to use to determine the file paths to return
+   * @returns An array of file paths matching the provided pattern(s)
+   */
+  globSync: (patterns: string | Omit<AssetGlob, "output"> | (string | Omit<AssetGlob, "output">)[]) => string[];
+  /**
+   * A helper function to resolve modules using the Jiti resolver
+   *
+   * @remarks
+   * This function can be used to resolve modules relative to the project root directory.
+   *
+   * @example
+   * ```ts
+   * const resolvedPath = await context.resolve("some-module", "/path/to/importer");
+   * ```
+   *
+   * @param id - The module to resolve.
+   * @param importer - An optional path to the importer module.
+   * @param options - Additional resolution options.
+   * @returns A promise that resolves to the resolved module path.
+   */
+  resolve: (id: string, importer?: string, options?: ResolveOptions$1) => Promise<string | undefined>;
+  /**
+   * A synchronous helper function to resolve modules using the Jiti resolver
+   *
+   * @remarks
+   * This function can be used to resolve modules relative to the project root directory.
+   *
+   * @example
+   * ```ts
+   * const resolvedPath = context.resolveSync("some-module", "/path/to/importer");
+   * ```
+   *
+   * @param id - The module to resolve.
+   * @param importer - An optional path to the importer module.
+   * @param options - Additional resolution options.
+   * @returns The resolved module path.
+   */
+  resolveSync: (id: string, importer?: string, options?: ResolveOptions$1) => string | undefined;
+  /**
+   * Resolves a given module ID using the configured aliases.
+   *
+   * @remarks
+   * This function can be used to map module IDs to different paths based on the alias configuration.
+   *
+   * @param id - The module ID to resolve.
+   * @returns The resolved module ID - after applying any configured aliases (this will be the same as the input ID if no aliases match).
+   */
+  resolveAlias: (id: string) => string;
+  /**
+   * Disposes of the virtual file system (VFS), writes any virtual file changes to disk, and releases any associated resources.
+   */
+  dispose: () => Promise<void>;
+}
+//#endregion
+//#region src/types/api.d.ts
+type BaseCommandType = ArrayValues<typeof BASE_EXECUTION_API_METHODS> | "finalize";
+type CommandType = ArrayValues<typeof SUPPORTED_COMMANDS>;
+type Commands<TContext extends Context = Context> = Record<CommandType, (this: TContext) => MaybePromise<void>>;
+type BaseExecutionApiMethods = (typeof BASE_EXECUTION_API_METHODS)[number];
+type ExecutionApiMethods = (typeof EXECUTION_API_METHODS)[number];
+type SupportedCommands = (typeof SUPPORTED_COMMANDS)[number];
+//#endregion
+//#region src/types/unplugin.d.ts
+type UnpluginBuilderVariant = "rollup" | "webpack" | "rspack" | "vite" | "esbuild" | "farm" | "unloader" | "rolldown" | "bun";
+type BuilderVariant = UnpluginBuilderVariant | "tsup" | "tsdown" | "unbuild";
+interface UnpluginOptions$1<TContext extends UnresolvedContext> extends UnpluginOptions {
+  /**
+   * An API object that can be used for inter-plugin communication.
+   *
+   * @see https://rollupjs.org/plugin-development/#direct-plugin-communication
+   */
+  context: TContext;
+}
+type UnpluginHookFunctions<TContext extends PluginContext = PluginContext, TUnpluginBuilderVariant extends UnpluginBuilderVariant = UnpluginBuilderVariant, TField extends keyof Required<UnpluginOptions$1<TContext>>[TUnpluginBuilderVariant] = keyof Required<UnpluginOptions$1<TContext>>[TUnpluginBuilderVariant]> = Required<UnpluginOptions$1<TContext>>[TUnpluginBuilderVariant][TField] extends infer THandler | {
+  handler: infer THandler;
+} ? THandler extends ((this: infer THandlerOriginalContext, ...args: infer THandlerArgs) => infer THandlerReturn) ? (this: THandlerOriginalContext & WithUnpluginBuildContext<TContext>, ...args: THandlerArgs) => THandlerReturn : THandler extends {
+  handler: infer THandlerFunction;
+} ? THandlerFunction extends ((this: infer THandlerFunctionOriginalContext, ...args: infer THandlerFunctionArgs) => infer THandlerFunctionReturn) ? (this: THandlerFunctionOriginalContext & WithUnpluginBuildContext<TContext>, ...args: THandlerFunctionArgs) => THandlerFunctionReturn : never : never : never;
+//#endregion
+//#region src/types/plugin.d.ts
+interface PluginHookObject<THookFunction extends AnyFunction, TFilter extends keyof HookFilter = never> {
+  /**
+   * The order in which the plugin should be applied.
+   */
+  order?: "pre" | "post" | null | undefined;
+  /**
+   * A filter to determine when the hook should be called.
+   */
+  filter?: Pick<HookFilter, TFilter>;
+  /**
+   * The hook function to be called.
+   */
+  handler: THookFunction;
+}
+type PluginHook<THookFunction extends AnyFunction, TFilter extends keyof HookFilter = never> = THookFunction | PluginHookObject<THookFunction, TFilter>;
+/**
+ * A result returned by the plugin from the `types` hook that describes the declaration types output file.
+ */
+interface TypesResult {
+  directives?: string[];
+  code: string;
+}
+interface Hooks<TContext extends PluginContext> {
+  /**
+   * A function that returns configuration options to be merged with the build context's options.
+   *
+   * @remarks
+   * Modify config before it's resolved. The hook can either mutate {@link Context.config} on the passed-in context directly, or return a partial config object that will be deeply merged into existing config.
+   *
+   * @warning User plugins are resolved before running this hook so injecting other plugins inside the config hook will have no effect.
+   *
+   * @see https://vitejs.dev/guide/api-plugin#config
+   *
+   * @param this - The build context.
+   * @param config - The partial configuration object to be modified.
+   * @returns A promise that resolves to a partial configuration object.
+   */
+  config: (this: UnresolvedContext<TContext["config"]>) => MaybePromise<DeepPartial$1<TContext["config"]> & Record<string, any>>;
+  /**
+   * Modify environment configs before it's resolved. The hook can either mutate the passed-in environment config directly, or return a partial config object that will be deeply merged into existing config.
+   *
+   * @remarks
+   * This hook is called for each environment with a partially resolved environment config that already accounts for the default environment config values set at the root level. If plugins need to modify the config of a given environment, they should do it in this hook instead of the config hook. Leaving the config hook only for modifying the root default environment config.
+   *
+   * @see https://vitejs.dev/guide/api-plugin#configenvironment
+   *
+   * @param this - The build context.
+   * @param name - The name of the environment being configured.
+   * @param environment - The Vite-like environment object containing information about the current build environment.
+   * @returns A promise that resolves when the hook is complete.
+   */
+  configEnvironment: (this: TContext, name: string, environment: EnvironmentConfig) => MaybePromise<Partial<ResolvedEnvironmentConfig> | undefined | null>;
+  /**
+   * A hook that is called when the plugin is resolved.
+   *
+   * @see https://vitejs.dev/guide/api-plugin#configresolved
+   *
+   * @param this - The build context.
+   * @returns A promise that resolves when the hook is complete.
+   */
+  configResolved: (this: TContext) => MaybePromise<void>;
+  /**
+   * A hook that is called to overwrite the generated declaration types file (.d.ts). The generated type definitions should describe the built-in modules/logic added during the `prepare` task.
+   *
+   * @param this - The build context.
+   * @param code - The source code to generate types for.
+   * @returns A promise that resolves when the hook is complete.
+   */
+  types: (this: TContext, code: string) => MaybePromise<TypesResult | string | undefined | null>;
+  /**
+   * A hook that is called at the start of the build process.
+   *
+   * @param this - The build context and unplugin build context.
+   * @returns A promise that resolves when the hook is complete.
+   */
+  buildStart: (this: BuildPluginContext<TContext["config"]> & TContext) => MaybePromise<void>;
+  /**
+   * A hook that is called at the end of the build process.
+   *
+   * @param this - The build context and unplugin build context.
+   * @returns A promise that resolves when the hook is complete.
+   */
+  buildEnd: (this: BuildPluginContext<TContext["config"]> & TContext) => MaybePromise<void>;
+  /**
+   * A hook that is called to transform the source code.
+   *
+   * @param this - The build context, unplugin build context, and unplugin context.
+   * @param code - The source code to transform.
+   * @param id - The identifier of the source code.
+   * @returns A promise that resolves when the hook is complete.
+   */
+  transform: (this: BuildPluginContext<TContext["config"]> & TContext, code: string, id: string) => MaybePromise<TransformResult>;
+  /**
+   * A hook that is called to load the source code.
+   *
+   * @param this - The build context, unplugin build context, and unplugin context.
+   * @param id - The identifier of the source code.
+   * @returns A promise that resolves when the hook is complete.
+   */
+  load: (this: BuildPluginContext<TContext["config"]> & TContext, id: string) => MaybePromise<LoadResult>;
+  /**
+   * A hook that is called to resolve the identifier of the source code.
+   *
+   * @param this - The build context, unplugin build context, and unplugin context.
+   * @param id - The identifier of the source code.
+   * @param importer - The importer of the source code.
+   * @param options - The options for resolving the identifier.
+   * @returns A promise that resolves when the hook is complete.
+   */
+  resolveId: (this: BuildPluginContext<TContext["config"]> & TContext, id: string, importer: string | undefined, options: {
+    isEntry: boolean;
+  }) => MaybePromise<string | ResolveResult | null | undefined>;
+  /**
+   * A hook that is called to write the bundle to disk.
+   *
+   * @param this - The build context.
+   * @returns A promise that resolves when the hook is complete.
+   */
+  writeBundle: (this: TContext) => MaybePromise<void>;
+}
+type HookFunctions<TContext extends PluginContext> = { [TCommandType in BaseCommandType]: (this: TContext) => MaybePromise<void> } & Hooks<TContext>;
+type DeepPartial$1<T> = { [K in keyof T]?: DeepPartial$1<T[K]> };
+type InferPluginHookFunction<TContext extends PluginContext, TKey extends string> = TKey extends keyof HookFunctions<TContext> ? HookFunctions<TContext>[TKey] extends AnyFunction ? PluginHook<HookFunctions<TContext>[TKey], TKey & keyof HookFilter> : HookFunctions<TContext>[TKey] extends object ? { [K in keyof HookFunctions<TContext>[TKey]]?: InferPluginHookFunction<TContext, `${TKey}:${K & string}`> } : never : never;
+type PluginHooks<TContext extends PluginContext> = { [TKey in keyof HookFunctions<TContext>]?: InferPluginHookFunction<TContext, TKey> } & {
+  types?: PluginHook<HookFunctions<TContext>["types"], never>;
+  transform?: PluginHook<HookFunctions<TContext>["transform"], "code" | "id">;
+  load?: PluginHook<HookFunctions<TContext>["load"], "id">;
+  resolveId?: PluginHook<HookFunctions<TContext>["resolveId"], "id">;
+};
+interface BasePlugin<TContext extends PluginContext> {
+  /**
+   * The name of the plugin, for use in deduplication, error messages and logs.
+   */
+  name: string;
+  /**
+   * An API object that can be used for inter-plugin communication.
+   *
+   * @see https://rollupjs.org/plugin-development/#direct-plugin-communication
+   */
+  api?: Record<string, any>;
+  /**
+   * Enforce plugin invocation tier similar to webpack loaders. Hooks ordering is still subject to the `order` property in the hook object.
+   *
+   * @remarks
+   * The Plugin invocation order is as follows:
+   * - `enforce: 'pre'` plugins
+   * - `order: 'pre'` plugin hooks
+   * - any other plugins (normal)
+   * - `order: 'post'` plugin hooks
+   * - `enforce: 'post'` plugins
+   *
+   * @see https://vitejs.dev/guide/api-plugin.html#plugin-ordering
+   * @see https://rollupjs.org/plugin-development/#build-hooks
+   * @see https://webpack.js.org/concepts/loaders/#enforce---pre-and-post
+   * @see https://esbuild.github.io/plugins/#concepts
+   */
+  enforce?: "pre" | "post";
+  /**
+   * A function to determine if two plugins are the same and can be de-duplicated.
+   *
+   * @remarks
+   * If this is not provided, plugins are de-duplicated by comparing their names.
+   *
+   * @param other - The other plugin to compare against.
+   * @returns `true` if the two plugins are the same, `false` otherwise.
+   */
+  dedupe?: false | ((other: Plugin<any>) => boolean);
+  /**
+   * Define environments where this plugin should be active. By default, the plugin is active in all environments.
+   *
+   * @param environment - The environment to check.
+   * @returns `true` if the plugin should be active in the specified environment, `false` otherwise.
+   */
+  applyToEnvironment?: (environment: ResolvedEnvironmentConfig) => boolean | PluginConfig<any>;
+  /**
+   * A function that returns configuration options to be merged with the build context's options.
+   *
+   * @remarks
+   * Modify config before it's resolved. The hook can either mutate {@link Context.config} on the passed-in context directly, or return a partial config object that will be deeply merged into existing config.
+   *
+   * @warning User plugins are resolved before running this hook so injecting other plugins inside the config hook will have no effect. If you want to add plugins, consider doing so in the {@link Plugin.dependsOn} property instead.
+   *
+   * @see https://vitejs.dev/guide/api-plugin#config
+   *
+   * @param this - The build context.
+   * @param config - The partial configuration object to be modified.
+   * @returns A promise that resolves to a partial configuration object.
+   */
+  config?: PluginHook<(this: UnresolvedContext<TContext["config"], TContext["system"]>) => MaybePromise<DeepPartial$1<TContext["config"]> & Record<string, any>>> | (DeepPartial$1<TContext["config"]> & Record<string, any>);
+}
+type Plugin<TContext extends PluginContext> = Partial<PluginHooks<TContext>> & BasePlugin<TContext> & Pick<UnpluginOptions$1<TContext>, UnpluginBuilderVariant>;
+type PluginNonHookFields = ArrayValues<typeof PLUGIN_NON_HOOK_FIELDS>;
+type PluginHookFields<TContext extends PluginContext = PluginContext, TKey extends string = string> = TKey extends ArrayValues<typeof PLUGIN_NON_HOOK_FIELDS> ? never : TKey extends keyof HookFunctions<TContext> ? HookFunctions<TContext>[TKey] extends AnyFunction ? TKey : HookFunctions<TContext>[TKey] extends object ? { [K in keyof HookFunctions<TContext>[TKey]]?: `${TKey}:${K & string}` }[keyof HookFunctions<TContext>[TKey]] : never : never;
+//#endregion
+//#region src/types/hooks.d.ts
+type HookListOrders = "preOrdered" | "preEnforced" | "normal" | "postEnforced" | "postOrdered";
+interface HooksListItem<TContext extends PluginContext = PluginContext, TFields extends string = string> {
+  plugin: Plugin<TContext>;
+  handler: InferHookFunction<TContext, TFields>;
+}
+type PluginFilter = (input: string) => boolean;
+type TransformHookFilter = (id: string, code: string) => boolean;
+interface NormalizedStringFilter {
+  include?: StringOrRegExp[];
+  exclude?: StringOrRegExp[];
+}
+type HooksList<TContext extends PluginContext = PluginContext, TFields extends string = string> = { [TKey in HookListOrders]?: HooksListItem<TContext, TFields>[] | undefined };
+type InferPluginFunction<TObject, TKey extends keyof Required<TObject>> = InferPluginFunctionKey<Required<TObject>[TKey]>;
+type InferPluginFunctionKey<TValue> = TValue extends AnyFunction ? TValue : TValue extends PluginHook<infer THookFunction, any> ? THookFunction : never;
+type InferHookFunction<TContext extends PluginContext, TKey extends string> = TKey extends `${infer TVariant}:${infer TField}` ? TVariant extends keyof Required<BasePlugin<TContext>> ? TField extends keyof Required<BasePlugin<TContext>>[TVariant] ? InferPluginFunction<Required<BasePlugin<TContext>>[TVariant], TField> : TVariant extends keyof Required<PluginHooks<TContext>> ? TField extends keyof Required<PluginHooks<TContext>>[TVariant] ? InferPluginFunction<Required<PluginHooks<TContext>>[TVariant], TField> : never : never : TVariant extends UnpluginBuilderVariant ? TField extends keyof Required<UnpluginOptions>[TVariant] ? UnpluginHookFunctions<TContext, TVariant, TField> : never : never : TKey extends keyof Required<BasePlugin<TContext>> ? InferPluginFunction<Required<BasePlugin<TContext>>, TKey> : TKey extends keyof Required<PluginHooks<TContext>> ? InferPluginFunction<Required<PluginHooks<TContext>>, TKey> : never;
+type InferHookReturnType<TContext extends PluginContext, TKey extends string> = ReturnType<InferHookFunction<TContext, TKey>>;
+type InferHookParameters<TContext extends PluginContext, TKey extends string> = Parameters<InferHookFunction<TContext, TKey>>;
+type InferHookThisType<TContext extends PluginContext, TKey extends string> = ThisParameterType<InferHookFunction<TContext, TKey>>;
+type CallHookOptions<TResult = any> = SelectHooksOptions & (({
+  /**
+   * Whether to call the hooks sequentially or in parallel.
+   *
+   * @defaultValue true
+   */
+  sequential?: true;
+} & ({
+  /**
+   * How to handle multiple return values from hooks.
+   * - "merge": Merge all non-undefined return values (if they are objects).
+   * - "first": Return the first non-undefined value.
+   * - "last": Return the last non-undefined value.
+   *
+   * @remarks
+   * Merging only works if the return values are objects.
+   *
+   * @defaultValue "merge"
+   */
+  result: "first";
+} | ({
+  /**
+   * An indicator specifying if the results of the previous hook should be provided as the **first** parameter of the next hook function, or a function to process the result of the previous hook function and pass the returned value as the next hook's **first** parameter
+   */
+  asNextParam?: false | ((previousResult: TResult) => MaybePromise<TResult>);
+} & ({
+  /**
+   * How to handle multiple return values from hooks.
+   * - "merge": Merge all non-undefined return values (if they are objects).
+   * - "first": Return the first non-undefined value.
+   * - "last": Return the last non-undefined value.
+   *
+   * @remarks
+   * Merging only works if the return values are objects.
+   *
+   * @defaultValue "merge"
+   */
+  result?: "merge";
+  /**
+   * A custom function to merge two sets of return values from hooks.
+   *
+   * @remarks
+   * If not provided, the {@link mergeResults} function will be used by default, which merges string results by concatenation and object results by deep merging.
+   *
+   * @param currentResult - The current hook result to merge with the previous results.
+   * @param previousResult - The previous hook result to merge with the current result.
+   * @returns The merged result.
+   */
+  merge?: (currentResult: TResult, previousResult: TResult) => MaybePromise<TResult>;
+} | {
+  /**
+   * How to handle multiple return values from hooks.
+   * - "merge": Merge all non-undefined return values (if they are objects).
+   * - "first": Return the first non-undefined value.
+   * - "last": Return the last non-undefined value.
+   *
+   * @remarks
+   * Merging only works if the return values are objects.
+   *
+   * @defaultValue "merge"
+   */
+  result?: "last";
+})))) | {
+  /**
+   * Whether to call the hooks sequentially or in parallel.
+   */
+  sequential: false;
+});
+//#endregion
+//#region src/types/logging.d.ts
+type LogLevel = (typeof LOG_LEVELS)[number];
+type LogCategory = (typeof LOG_CATEGORIES)[number];
+interface LogMeta {
+  /**
+   * A unique identifier for the log message, which can be used to correlate related log entries across different parts of the system or different executions.
+   */
+  logId: string;
+  /**
+   * The log level of the message, which indicates the severity or importance of the log entry. The log level can be used to filter log messages based on their importance, allowing users to focus on critical issues or relevant information while ignoring less important messages.
+   */
+  type: LogLevel;
+  /**
+   * The category of the log message, which can be used to classify and filter log entries based on their purpose or origin.
+   */
+  category: LogCategory;
+  /**
+   * The timestamp when the RPC message was created, represented as the number of milliseconds since the Unix epoch.
+   */
+  timestamp: number;
+  /**
+   * The name of the project or package associated with the log message, which can be used to identify the source of the log entry and provide context for the message.
+   */
+  name?: string;
+  /**
+   * A unique identifier for the current execution instance, which can be used for logging and other purposes to distinguish between different executions in the same process.
+   */
+  executionId?: string;
+  /**
+   * The zero-based index of the current execution within the sequence of executions in the same process.
+   */
+  configIndex?: number;
+  /**
+   * Optional command identifier to specify the command or task associated with the log message, which can be used to provide additional context about the operation being performed when the log entry was generated.
+   */
+  command?: string;
+  /**
+   * Optional hook name to specify the plugin hook associated with the log message, which can be used to provide additional context about the specific plugin hook being executed when the log entry was generated.
+   */
+  hook?: string;
+  /**
+   * Optional environment identifier to specify the context or environment in which the message is being processed.
+   */
+  environment?: string;
+  /**
+   * Optional plugin name to specify the source plugin of the log message.
+   */
+  plugin?: string;
+  /**
+   * The name of the logger or source of the log message, which can be used to identify the origin of the log entry.
+   */
+  source?: string;
+  /**
+   * Indicates whether the log message is related to inter-process communication (IPC).
+   *
+   * @internal
+   */
+  $$ipc?: boolean;
+}
+type LogFnOptions = Omit<Partial<LogMeta>, "logId" | "timestamp" | "name" | "type"> & {
+  mode?: Mode;
+  logLevel?: LogLevelUserConfig;
+};
+type LogFnMeta = LogLevel | PartialKeys<LogMeta, "logId" | "timestamp" | "name" | "category">;
+type LogFn = (meta: LogFnMeta, message: string) => void;
+type LoggerMeta = PartialKeys<Omit<LogMeta, "type">, "logId" | "timestamp" | "name" | "category">;
+type LoggerOptions = Omit<LoggerMeta, "logId" | "timestamp" | "type"> & {
+  mode?: Mode;
+  logLevel?: LogLevelUserConfig;
+};
+interface PowerlinesMessage<TMeta> extends UnpluginMessage {
+  meta: TMeta;
+  error?: Error;
+}
+type LogMessage = PowerlinesMessage<Partial<LogMeta>>;
+/**
+ * A type representing a log message that can be passed to the logging methods defined in the {@link Logger} interface, which includes the log metadata and message content. This type is used as the parameter for the logging methods defined in the {@link Logger} interface, allowing users to log messages with rich metadata that can be used for filtering, formatting, or other purposes in the logging implementation.
+ */
+type LoggerMessage = PowerlinesMessage<LoggerMeta>;
+/**
+ * An internal interface representing a logger instance used within Powerlines for logging messages at various log levels, including "error", "warn", "info", "debug", and "trace". This interface defines methods for logging messages at each log level, which accept a message parameter that can be either a string or an object containing the log metadata and message content. The logger instance also includes an options property that contains the configuration options used for the logger, such as the source, command, environment, plugin, log level, and other relevant metadata. This interface is intended for internal use within Powerlines and is not meant to be implemented by users directly; instead, users can provide a custom logger that implements the {@link CustomLogger} interface to integrate with Powerlines' logging system.
+ */
+interface Logger {
+  options: LoggerOptions;
+  error: (message: string | LoggerMessage | Error) => void;
+  warn: (message: string | LoggerMessage) => void;
+  info: (message: string | LoggerMessage) => void;
+  debug: (message: string | LoggerMessage) => void;
+  trace: (message: string | LoggerMessage) => void;
+  log: (type: LogLevel, message: string | LoggerMessage) => void;
+}
+/**
+ * A type representing a log message that can be passed to a custom logger, which includes the log metadata and message content. This type is used as the parameter for the logging methods defined in the {@link CustomLogger} interface, allowing users to log messages with rich metadata that can be used for filtering, formatting, or other purposes in their custom logging implementation.
+ */
+type CustomLoggerMessage = PowerlinesMessage<Omit<LogMeta, "type">>;
+/**
+ * An interface representing a custom logger that can be provided by the user to override the default logging behavior of Powerlines. This interface defines methods for logging messages at different log levels, including "error", "warn", "info", "debug", and "trace". Each method accepts a message parameter, which can be either a string or an object containing the log metadata and message content. By implementing this interface, users can integrate their own logging system with Powerlines or customize the logging behavior to suit their specific needs.
+ */
+interface CustomLogger {
+  /**
+   * A function to log messages at the "error" level, which indicates a serious issue that has caused a failure in the build process or a critical problem that needs immediate attention.
+   *
+   * @param message - The log message to be recorded, which can be a string or an object containing the log metadata and message content. The log message should provide sufficient information to understand the context and nature of the error being reported.
+   * @returns void
+   */
+  error?: (message: CustomLoggerMessage) => void;
+  /**
+   * A function to log messages at the "warn" level, which indicates a potential issue or a situation that may require attention but does not necessarily cause a failure in the build process.
+   *
+   * @param message - The log message to be recorded, which can be a string or an object containing the log metadata and message content. The log message should provide sufficient information to understand the context and nature of the warning being reported.
+   * @returns void
+   */
+  warn?: (message: CustomLoggerMessage) => void;
+  /**
+   * A function to log messages at the "info" level, which indicates general informational messages about the build process, such as the start and completion of tasks, configuration details, or other relevant information that may be useful for monitoring the build process.
+   *
+   * @param message - The log message to be recorded, which can be a string or an object containing the log metadata and message content. The log message should provide sufficient information to understand the context and nature of the informational message being reported.
+   * @returns void
+   */
+  info?: (message: CustomLoggerMessage) => void;
+  /**
+   * A function to log messages at the "debug" level, which indicates detailed debugging information that may be useful for diagnosing issues during development or troubleshooting problems in the build process.
+   *
+   * @param message - The log message to be recorded, which can be a string or an object containing the log metadata and message content. The log message should provide sufficient information to understand the context and nature of the debug information being reported.
+   * @returns void
+   */
+  debug?: (message: CustomLoggerMessage) => void;
+  /**
+   * A function to log messages at the "trace" level, which indicates very detailed tracing information that may be useful for in-depth analysis of the build process or for tracking the flow of execution through various stages of the build.
+   *
+   * @param message - The log message to be recorded, which can be a string or an object containing the log metadata and message content. The log message should provide sufficient information to understand the context and nature of the trace information being reported.
+   * @returns void
+   */
+  trace?: (message: CustomLoggerMessage) => void;
+}
+type LogLevelUserConfig = LogLevel | RequiredKeys<Partial<Record<LogCategory, LogLevel | boolean | undefined>>, "general">;
+type LogLevelResolvedConfig = Record<LogCategory, LogLevel>;
+//#endregion
+//#region src/types/tsconfig.d.ts
+type ReflectionMode = "default" | "explicit" | "never";
+type RawReflectionMode = ReflectionMode | "" | boolean | string | string[] | undefined;
+/**
+ * Defines the level of reflection to be used during the transpilation process.
+ *
+ * @remarks
+ * The level determines how much extra data is captured in the byte code for each type. This can be one of the following values:
+ * - `minimal` - Only the essential type information is captured.
+ * - `default` - Additional type information is captured, including some contextual data.
+ * - `extended` - Even more detailed type information is captured, including extended contextual data.
+ * - `all` - All available type information is captured, including detailed contextual data.
+ */
+type Level = "minimal" | "default" | "extended" | "all";
+interface DeepkitOptions {
+  /**
+   * Either true to activate reflection for all files compiled using this tsconfig,
+   * or a list of globs/file paths relative to this tsconfig.json.
+   * Globs/file paths can be prefixed with a ! to exclude them.
+   */
+  reflection?: RawReflectionMode;
+  /**
+   * Defines the level of reflection to be used during the transpilation process.
+   *
+   * @remarks
+   * The level determines how much extra data is captured in the byte code for each type. This can be one of the following values:
+   * - `minimal` - Only the essential type information is captured. (only "hidden", "ignore" and "internal", "readonly")
+   * - `default` - Additional type information is captured, including some contextual data. (adds "alias" and "runtime")
+   * - `extended` - Even more detailed type information is captured, including extended contextual data. (adds "permissions" and "domain")
+   * - `all` - All available type information is captured, including detailed contextual data. (adds "title" and "description")
+   */
+  level?: Level;
+}
+type TSCompilerOptions = CompilerOptions & DeepkitOptions;
+/**
+ * The TypeScript compiler configuration.
+ *
+ * @see https://www.typescriptlang.org/docs/handbook/tsconfig-json.html
+ */
+interface TSConfig extends Omit<TsConfigJson, "reflection"> {
+  /**
+   * Either true to activate reflection for all files compiled using this tsconfig,
+   * or a list of globs/file paths relative to this tsconfig.json.
+   * Globs/file paths can be prefixed with a ! to exclude them.
+   */
+  reflection?: RawReflectionMode;
+  /**
+   * Defines the level of reflection to be used during the transpilation process.
+   *
+   * @remarks
+   * The level determines how much extra data is captured in the byte code for each type. This can be one of the following values:
+   * - `minimal` - Only the essential type information is captured.
+   * - `default` - Additional type information is captured, including some contextual data.
+   * - `extended` - Even more detailed type information is captured, including extended contextual data.
+   * - `all` - All available type information is captured, including detailed contextual data.
+   */
+  level?: Level;
+  /**
+   * Instructs the TypeScript compiler how to compile `.ts` files.
+   */
+  compilerOptions?: TSCompilerOptions;
+}
+type ParsedTypeScriptConfig = ts.ParsedCommandLine & {
+  originalTsconfigJson: TsConfigJson;
+  tsconfigJson: TSConfig;
+  tsconfigFilePath: string;
+};
+//#endregion
+//#region src/types/context.d.ts
+type MetaInfo = Record<string, any> & {
+  /**
+   * The checksum generated from the resolved options
+   */
+  checksum: string;
+  /**
+   * The unique identifier of the execution, which can be used for logging and other purposes to distinguish between different executions in the same process.
+   */
+  executionId: string;
+  /**
+   * The build id, which is a unique identifier for the current build process. This can be used for logging and other purposes to distinguish between different builds in the same process.
+   */
+  buildId: string;
+  /**
+   * The release id, which is a unique identifier for the current release. This can be used for logging and other purposes to distinguish between different releases in the same process.
+   */
+  releaseId: string;
+  /**
+   * The timestamp when the execution context was initialized
+   */
+  timestamp: number;
+  /**
+   * A hash that represents the path to the project root directory
+   */
+  rootHash: string;
+  /**
+   * A hash that represents the path to the configuration root directory
+   */
+  configHash: string;
+};
+interface Resolver extends Jiti {
+  plugin: Jiti;
+}
+interface TransformResult$1 {
+  code: string;
+  map: SourceMap | null;
+}
+/**
+ * The format for providing source code to the compiler
+ */
+interface SourceFile {
+  /**
+   * The name of the file to be compiled
+   */
+  id: string;
+  /**
+   * The source code to be compiled
+   */
+  code: MagicString;
+  /**
+   * The environment variables used in the source code
+   */
+  env: string[];
+  /**
+   * The result of the transformation
+   */
+  result?: TransformResult$1;
+}
+type UnimportContext = Omit<Unimport, "injectImports"> & {
+  dumpImports: () => Promise<void>;
+  injectImports: (source: SourceFile) => Promise<SourceFile>;
+  refreshRuntimeImports: () => Promise<void>;
+};
+interface SelectHooksOptions {
+  order?: "pre" | "post" | "normal";
+}
+/**
+ * Options for initializing or updating the context with new configuration values
+ */
+interface InitContextOptions {
+  /**
+   * If false, the plugin will be loaded after all other plugins.
+   *
+   * @defaultValue true
+   */
+  isHighPriority: boolean;
+}
+/**
+ * Options for fetch requests made via the context's {@link Context.fetch} method
+ */
+interface FetchOptions extends RequestInit {
+  /**
+   * An indicator specifying that the request should bypass any caching
+   */
+  skipCache?: boolean;
+  /**
+   * The maximum time in milliseconds to wait for the request to complete.
+   *
+   * @defaultValue 30000
+   */
+  timeout?: number;
+}
+/**
+ * Options for parsing code using [Oxc-Parser](https://github.com/oxc/oxc)
+ */
+interface ParseOptions extends ParserOptions {
+  /**
+   * When true this allows return statements to be outside functions to e.g. support parsing CommonJS code.
+   */
+  allowReturnOutsideFunction?: boolean;
+}
+interface EmitOptions extends WriteOptions {
+  /**
+   * The file extension to use when emitting the file
+   */
+  extension?: string;
+  /**
+   * If true, will emit the file using {@link UnpluginBuildContext.emitFile | the bundler's emit function}.
+   */
+  emitWithBundler?: boolean;
+  needsCodeReference?: Parameters<UnpluginBuildContext["emitFile"]>[0]["needsCodeReference"];
+  originalFileName?: Parameters<UnpluginBuildContext["emitFile"]>[0]["originalFileName"];
+}
+/**
+ * Options for emitting entry virtual files
+ */
+type EmitEntryOptions = EmitOptions & Omit<ResolvedEntryFileReference, "file">;
+interface ResolveResult extends ExternalIdResult {
+  /**
+   * A flag indicating whether the resolved module is part of the generated runtime modules
+   */
+  virtual?: boolean;
+}
+/**
+ * The base Powerlines context.
+ *
+ * @remarks
+ * This context provides the foundational structure for interacting with the Powerlines engine.
+ */
+interface BaseContext<TSystemContext = any> extends Pick<Required<Options>, "cwd"> {
+  /**
+   * The system instance associated with the context, which can be used to interact with the Powerlines engine and perform various operations during the build process. The specific type of the system may vary depending on the environment and use case, but it typically provides methods for logging, file system operations, and other interactions with the Powerlines engine.
+   */
+  system: TSystemContext;
+  /**
+   * The timestamp when the context was initialized
+   */
+  timestamp: number;
+  /**
+   * The Powerlines environment paths
+   */
+  envPaths: EnvPaths;
+  /**
+   * The file system path to the Powerlines package installation
+   */
+  powerlinesPath: string;
+  /**
+   * The options provided to the Powerlines process.
+   */
+  options: Options;
+  /**
+   * An instance of the Powerlines logger client that can be used to generate log messages with consistent formatting and metadata.
+   */
+  logger: Logger;
+  /**
+   * A logging function for fatal messages
+   */
+  fatal: (message: string | LogMessage | Error) => void;
+  /**
+   * A logging function for error messages
+   */
+  error: (message: string | LogMessage | Error) => void;
+  /**
+   * A logging function for warning messages
+   */
+  warn: (message: string | LogMessage) => void;
+  /**
+   * A logging function for informational messages
+   */
+  info: (message: string | LogMessage) => void;
+  /**
+   * A logging function for debug messages
+   */
+  debug: (message: string | LogMessage) => void;
+  /**
+   * A logging function for trace messages
+   */
+  trace: (message: string | LogMessage) => void;
+  /**
+   * A function to create a timer for measuring the duration of asynchronous operations
+   *
+   * @example
+   * ```ts
+   * const stopTimer = context.timer("Your Async Operation");
+   * await performAsyncOperation();
+   * stopTimer(); // "Your Async Operation completed in 123.45 milliseconds"
+   * ```
+   *
+   * @param name - The name of the timer.
+   * @returns A function that, when called, stops the timer and logs the duration.
+   */
+  timer: (name: string) => () => void;
+  /**
+   * Create a new logger instance
+   *
+   * @param options - The configuration options to use for the logger instance, which can be used to customize the appearance and behavior of the log messages generated by the logger. This is typically the name of the plugin or module that is creating the logger instance.
+   * @returns A logger client instance that can be used to generate log messages with consistent formatting and metadata.
+   */
+  createLogger: (options: LoggerOptions, logFn?: LogFn) => Logger;
+  /**
+   * Extend the current logger instance with a new source
+   *
+   * @param options - The overlay metadata to use for the badge in the log output.
+   * @returns A logger client instance that extends the current logger with the provided configuration options.
+   */
+  extendLogger: (options: LoggerOptions, logFn?: LogFn) => Logger;
+}
+/**
+ * The unresolved Powerlines context.
+ *
+ * @remarks
+ * This context is used before the user configuration has been fully resolved after the `config`.
+ */
+interface UnresolvedContext<TResolvedConfig extends ResolvedConfig$1 = ResolvedConfig$1, TSystemContext = any> extends BaseContext<TSystemContext> {
+  /**
+   * The options provided to the Powerlines process, resolved with default values and merged with any configuration provided by plugins or other sources. This is typically the final configuration used during the build process, but may also include additional options that are relevant to the context and its interactions with the Powerlines engine.
+   */
+  options: ExecutionOptions;
+  /**
+   * An object containing the options provided to Powerlines
+   */
+  config: Omit<TResolvedConfig, "pluginConfig">;
+  /**
+   * A place to store metadata information on the context for access in plugins and other parts of the system. This can be used to store information about the current execution, such as a unique identifier for the execution, timestamps, or any other relevant data that may be useful for plugins or other parts of the system to access during the build process.
+   */
+  meta: MetaInfo;
+  /**
+   * The metadata information currently written to disk
+   */
+  persistedMeta?: MetaInfo;
+  /**
+   * The path to a directory where the reflection data buffers (used by the build processes) are stored
+   */
+  readonly dataPath: string;
+  /**
+   * The path to a directory where the project cache (used by the build processes) is stored
+   */
+  readonly cachePath: string;
+  /**
+   * The Powerlines artifacts directory
+   */
+  readonly artifactsPath: string;
+  /**
+   * The path to the Powerlines builtin runtime modules directory
+   */
+  readonly builtinsPath: string;
+  /**
+   * The path to the Powerlines entry modules directory
+   */
+  readonly entryPath: string;
+  /**
+   * The path to the Powerlines infrastructure modules directory
+   */
+  readonly infrastructurePath: string;
+  /**
+   * The path to the Powerlines TypeScript declaration files directory
+   */
+  readonly typesPath: string;
+  /**
+   * Invokes the configured plugin hooks
+   *
+   * @remarks
+   * By default, it will call the `"pre"`, `"normal"`, and `"post"` ordered hooks in sequence
+   *
+   * @param hook - The hook to call
+   * @param options - The options to provide to the hook
+   * @param args - The arguments to pass to the hook
+   * @returns The result of the hook call
+   */
+  callHook: <TKey extends string>(hook: TKey, options: CallHookOptions & {
+    environment?: string | EnvironmentContext<TResolvedConfig>;
+  }, ...args: InferHookParameters<PluginContext<TResolvedConfig>, TKey>) => Promise<InferHookReturnType<PluginContext<TResolvedConfig>, TKey> | undefined>;
+  /**
+   * The virtual file system interface for managing files during the build process
+   */
+  fs: VirtualFileSystemInterface;
+  /**
+   * The project's `package.json` file content
+   */
+  packageJson: PackageJson & Record<string, any>;
+  /**
+   * The project's `project.json` file content
+   */
+  projectJson?: Record<string, any>;
+  /**
+   * The dependency installations required by the project
+   */
+  dependencies: Record<string, string | Range>;
+  /**
+   * The development dependency installations required by the project
+   */
+  devDependencies: Record<string, string | Range>;
+  /**
+   * The parsed TypeScript configuration from the `tsconfig.json` file
+   */
+  tsconfig: ParsedTypeScriptConfig;
+  /**
+   * The entry points of the source code
+   */
+  entry: ResolvedEntryFileReference[];
+  /**
+   * The Jiti module resolver
+   */
+  resolver: Resolver;
+  /**
+   * The builtin module id that exist in the Powerlines virtual file system
+   */
+  builtins: string[];
+  /**
+   * The alias mappings for the project used during module resolution
+   *
+   * @remarks
+   * This includes both the built-in module aliases as well as any custom aliases defined in the build configuration.
+   */
+  alias: Record<string, string>;
+  /**
+   * The resolved tsconfig file paths for the project
+   */
+  resolvePatterns: RegExp[];
+  /**
+   * Additional arguments provided during execution of the command, such as CLI flags or other parameters that may be relevant to the command being executed.
+   */
+  additionalArgs: Record<string, string | string[]>;
+  /**
+   * A function to perform HTTP fetch requests
+   *
+   * @remarks
+   * This function uses a caching layer to avoid duplicate requests during the Powerlines process.
+   *
+   * @example
+   * ```ts
+   * const response = await context.fetch("https://api.example.com/data");
+   * const data = await response.json();
+   * ```
+   *
+   * @see https://github.com/nodejs/undici
+   *
+   * @param input - The URL to fetch.
+   * @param options - The fetch request options.
+   * @returns A promise that resolves to a response returned by the fetch.
+   */
+  fetch: (input: RequestInfo, options?: FetchOptions) => Promise<Response>;
+  /**
+   * Parse code using [Oxc-Parser](https://github.com/oxc/oxc) into an (ESTree-compatible)[https://github.com/estree/estree] AST object.
+   *
+   * @remarks
+   * This function can be used to parse TypeScript code into an AST for further analysis or transformation.
+   *
+   * @example
+   * ```ts
+   * const ast = context.parse("const x: number = 42;");
+   * ```
+   *
+   * @see https://rollupjs.org/plugin-development/#this-parse
+   * @see https://github.com/oxc/oxc
+   *
+   * @param code - The source code to parse.
+   * @param options - The options to pass to the parser.
+   * @returns An (ESTree-compatible)[https://github.com/estree/estree] AST object.
+   */
+  parse: (code: string, options?: ParseOptions) => Promise<ParseResult>;
+  /**
+   * A helper function to resolve modules using the Jiti resolver
+   *
+   * @remarks
+   * This function can be used to resolve modules relative to the project root directory.
+   *
+   * @example
+   * ```ts
+   * const resolvedPath = await context.resolve("some-module", "/path/to/importer");
+   * ```
+   *
+   * @param id - The module to resolve.
+   * @param importer - An optional path to the importer module.
+   * @param options - Additional resolution options.
+   * @returns A promise that resolves to the resolved module path.
+   */
+  resolve: (id: string, importer?: string, options?: ResolveOptions$1) => Promise<ResolveResult | undefined>;
+  /**
+   * A helper function to load modules using the Jiti resolver
+   *
+   * @remarks
+   * This function can be used to load modules relative to the project root directory.
+   *
+   * @example
+   * ```ts
+   * const module = await context.load("some-module", "/path/to/importer");
+   * ```
+   *
+   * @param id - The module to load.
+   * @returns A promise that resolves to the loaded module.
+   */
+  load: (id: string) => Promise<TransformResult$1 | undefined>;
+  /**
+   * The Powerlines builtin virtual files
+   */
+  getBuiltins: () => Promise<VirtualFile[]>;
+  /**
+   * Resolves a file and writes it to the VFS if it does not already exist
+   *
+   * @param code - The source code of the file
+   * @param path - The path to write the file to
+   * @param options - Additional options for writing the file
+   */
+  emit: (code: string, path: string, options?: EmitOptions) => Promise<void>;
+  /**
+   * Synchronously resolves a file and writes it to the VFS if it does not already exist
+   *
+   * @param code - The source code of the file
+   * @param path - The path to write the file to
+   * @param options - Additional options for writing the file
+   */
+  emitSync: (code: string, path: string, options?: EmitOptions) => void;
+  /**
+   * Resolves a builtin virtual file and writes it to the VFS if it does not already exist
+   *
+   * @param code - The source code of the builtin file
+   * @param id - The unique identifier of the builtin file
+   * @param options - Additional options for writing the builtin file
+   */
+  emitBuiltin: (code: string, id: string, options?: EmitOptions) => Promise<void>;
+  /**
+   * Synchronously resolves a builtin virtual file and writes it to the VFS if it does not already exist
+   *
+   * @param code - The source code of the builtin file
+   * @param id - The unique identifier of the builtin file
+   * @param options - Additional options for writing the builtin file
+   */
+  emitBuiltinSync: (code: string, id: string, options?: EmitOptions) => void;
+  /**
+   * Resolves a entry virtual file and writes it to the VFS if it does not already exist
+   *
+   * @param code - The source code of the entry file
+   * @param path - An optional path to write the entry file to
+   * @param options - Additional options for writing the entry file
+   */
+  emitEntry: (code: string, path: string, options?: EmitEntryOptions) => Promise<void>;
+  /**
+   * Synchronously resolves a entry virtual file and writes it to the VFS if it does not already exist
+   *
+   * @param code - The source code of the entry file
+   * @param path - An optional path to write the entry file to
+   * @param options - Additional options for writing the entry file
+   */
+  emitEntrySync: (code: string, path: string, options?: EmitEntryOptions) => void;
+  /**
+   * Resolves a infrastructure virtual file and writes it to the VFS if it does not already exist
+   *
+   * @param code - The source code of the infrastructure file
+   * @param id - The unique identifier of the infrastructure file
+   * @param options - Additional options for writing the infrastructure file
+   */
+  emitInfrastructure: (code: string, id: string, options?: EmitOptions) => Promise<void>;
+  /**
+   * Synchronously resolves a infrastructure virtual file and writes it to the VFS if it does not already exist
+   *
+   * @param code - The source code of the infrastructure file
+   * @param id - The unique identifier of the infrastructure file
+   * @param options - Additional options for writing the infrastructure file
+   */
+  emitInfrastructureSync: (code: string, id: string, options?: EmitOptions) => void;
+  /**
+   * Generates a checksum representing the current context state
+   *
+   * @returns A promise that resolves to a string representing the checksum
+   */
+  generateChecksum: () => Promise<string>;
+}
+/**
+ * The resolved Powerlines context.
+ *
+ * @remarks
+ * This context is used after the user configuration has been fully resolved and merged with default values, providing access to the final configuration options and utility functions for interacting with the Powerlines engine.
+ */
+type Context<TResolvedConfig extends ResolvedConfig$1 = ResolvedConfig$1, TSystemContext = any> = Omit<UnresolvedContext<TResolvedConfig, TSystemContext>, "config" | "callHook"> & {
+  /**
+   * The fully resolved Powerlines configuration
+   */
+  config: TResolvedConfig;
+  /**
+   * A setter function to populate the plugin config values provided during execution of the command, such as CLI flags or other parameters that may be relevant to the command being executed. This function can be used to update the context with the plugin configuration values, which may be used during the configuration resolution process to ensure that the final configuration reflects both the user configuration and any plugin configuration provided during execution.
+   *
+   * @param config - The plugin configuration values to set.
+   * @returns A promise that resolves when the plugin configuration values have been set.
+   */
+  setPluginConfig: (config: DeepPartial<UserConfig>) => Promise<void>;
+  /**
+   * Invokes the configured plugin hooks
+   *
+   * @remarks
+   * By default, it will call the `"pre"`, `"normal"`, and `"post"` ordered hooks in sequence
+   *
+   * @param hook - The hook to call
+   * @param options - The options to provide to the hook
+   * @param args - The arguments to pass to the hook
+   * @returns The result of the hook call
+   */
+  callHook: <TKey extends string>(hook: TKey, options: CallHookOptions & {
+    environment?: string | EnvironmentContext<any, any>;
+  }, ...args: InferHookParameters<PluginContext<any, any>, TKey>) => Promise<InferHookReturnType<PluginContext<any, any>, TKey> | undefined>;
+};
+interface ExecutionContext<TResolvedConfig extends ResolvedConfig$1 = ResolvedConfig$1, TSystemContext = any> extends Context<TResolvedConfig, TSystemContext> {
+  /**
+   * The unique identifier of the execution context, which can be used for logging and other purposes to distinguish between different executions in the same process.
+   */
+  readonly id: string;
+  /**
+   * The expected plugins options for the Powerlines project.
+   *
+   * @remarks
+   * This is a record of plugin identifiers to their respective options. This field is populated by the Powerlines engine during both plugin initialization and the `init` command.
+   */
+  plugins: Plugin<PluginContext<TResolvedConfig, TSystemContext>>[];
+  /**
+   * A table for storing the current context for each configured environment
+   */
+  environments: Record<string, EnvironmentContext<TResolvedConfig, TSystemContext>>;
+  /**
+   * Retrieves the context for a specific environment by name
+   *
+   * @throws Will throw an error if the environment does not exist
+   *
+   * @param name - The name of the environment to retrieve. If not provided, the default environment is returned.
+   * @returns A promise that resolves to the environment context.
+   *
+   * @example
+   * ```ts
+   * const devEnv = await apiContext.getEnvironment("development");
+   * const defaultEnv = await apiContext.getEnvironment();
+   * ```
+   */
+  getEnvironment: (name?: string) => Promise<EnvironmentContext<TResolvedConfig, TSystemContext>>;
+  /**
+   * Safely retrieves the context for a specific environment by name
+   *
+   * @param name - The name of the environment to retrieve. If not provided, the default environment is returned.
+   * @returns A promise that resolves to the environment context, or undefined if the environment does not exist.
+   *
+   * @example
+   * ```ts
+   * const devEnv = await apiContext.getEnvironmentSafe("development");
+   * const defaultEnv = await apiContext.getEnvironmentSafe();
+   * ```
+   *
+   * @remarks
+   * This method is similar to `getEnvironment`, but it returns `undefined` instead of throwing an error if the specified environment does not exist.
+   * This can be useful in scenarios where the existence of an environment is optional or uncertain.
+   *
+   * ```ts
+   * const testEnv = await apiContext.getEnvironmentSafe("test");
+   * if (testEnv) {
+   *   // Environment exists, safe to use it
+   * } else {
+   *   // Environment does not exist, handle accordingly
+   * }
+   * ```
+   *
+   * Using this method helps avoid unhandled exceptions in cases where an environment might not be defined.
+   */
+  getEnvironmentSafe: (name?: string) => Promise<EnvironmentContext<TResolvedConfig, TSystemContext> | undefined>;
+  /**
+   * A function to copy the context and update the fields for a specific environment
+   *
+   * @param environment - The environment configuration to use.
+   * @returns A new context instance with the updated environment.
+   */
+  createEnvironment: (environment: EnvironmentResolvedConfig<TResolvedConfig>["environment"]) => Promise<EnvironmentContext<TResolvedConfig, TSystemContext>>;
+  /**
+   * A function to merge all configured environments into a single context
+   *
+   * @returns A promise that resolves to the merged environment context.
+   */
+  toEnvironment: () => Promise<EnvironmentContext<TResolvedConfig, TSystemContext>>;
+  /**
+   * A function used internally to add a plugin to the context and update the configuration options
+   *
+   * @danger
+   * This field is for internal use only and should not be accessed or modified directly. It is unstable and can be changed at anytime.
+   *
+   * @internal
+   */
+  unstable_addPlugin: (plugin: PluginConfig<PluginContext<TResolvedConfig, TSystemContext>>) => Promise<void>;
+}
+interface EnvironmentPlugin<TResolvedConfig extends ResolvedConfig$1 = ResolvedConfig$1, TSystemContext = any> extends Plugin<PluginContext<TResolvedConfig, TSystemContext>> {
+  /**
+   * A internal field to store the plugin configuration and context for the environment context
+   *
+   * @danger
+   * This field is for internal use only and should not be accessed or modified directly. It is unstable and can be changed at anytime.
+   *
+   * @internal
+   */
+  "~internal": {
+    /**
+     * The unique identifier of the plugin, which can be used for logging and other purposes to distinguish between different plugins in the same process.
+     */
+    readonly id: string;
+    /**
+     * The context for the plugin, which provides access to the Powerlines engine and other utilities for interacting with the build process.
+     *
+     * @remarks
+     * This context is specific to the plugin and environment, allowing for environment-specific modifications without affecting the global context.
+     */
+    readonly context: PluginContext<TResolvedConfig, TSystemContext>;
+  };
+}
+type SelectHookResultItem<TContext extends PluginContext, TKey extends string> = HooksListItem<TContext, TKey> & {
+  context: TContext;
+};
+type SelectHookResult<TContext extends PluginContext, TKey extends string> = SelectHookResultItem<TContext, TKey>[];
+interface EnvironmentContext<TResolvedConfig extends ResolvedConfig$1 = ResolvedConfig$1, TSystemContext = any> extends Context<EnvironmentResolvedConfig<TResolvedConfig>, TSystemContext> {
+  /**
+   * The unique identifier of the environment associated with this context, which can be used for logging and other purposes to distinguish between different environments in the same process.
+   */
+  readonly id: string;
+  /**
+   * The expected plugins options for the Powerlines project.
+   *
+   * @remarks
+   * This is a record of plugin identifiers to their respective options. This field is populated by the Powerlines engine during both plugin initialization and the `init` command.
+   */
+  plugins: EnvironmentPlugin<TResolvedConfig, TSystemContext>[];
+  /**
+   * A table holding references to hook functions registered by plugins
+   */
+  hooks: HooksList<PluginContext<TResolvedConfig, TSystemContext>>;
+  /**
+   * The execution context associated with this environment, which provides access to the project configuration, environment, and utility functions for performing the build. The execution context is used to manage the state and behavior of the build process across multiple environments, allowing for hooks to be called at different stages of the build and for environment-specific configurations to be applied.
+   *
+   * @danger
+   * This field is for internal use only and should not be accessed or modified directly. It is unstable and can be changed at anytime.
+   *
+   * @internal
+   */
+  unstable_execution: ExecutionContext<TResolvedConfig, TSystemContext>;
+  /**
+   * Retrieves the hook handlers for a specific hook name
+   */
+  selectHooks: <TKey extends string>(key: TKey, options?: SelectHooksOptions) => SelectHookResult<PluginContext<TResolvedConfig, TSystemContext>, TKey>;
+  /**
+   * A function used internally to add a plugin to the context and update the configuration options
+   *
+   * @danger
+   * This field is for internal use only and should not be accessed or modified directly. It is unstable and can be changed at anytime.
+   *
+   * @internal
+   */
+  unstable_addPlugin: (plugin: PluginConfig<PluginContext<TResolvedConfig, TSystemContext>>) => Promise<void>;
+}
+interface PluginContext<out TResolvedConfig extends ResolvedConfig$1 = ResolvedConfig$1, TSystemContext = any> extends Context<EnvironmentResolvedConfig<TResolvedConfig>, TSystemContext> {
+  /**
+   * The unique identifier of the plugin associated with this context, which can be used for logging and other purposes to distinguish between different plugins in the same process.
+   */
+  readonly id: string;
+  /**
+   * The context for the environment associated with this plugin context, which provides access to the Powerlines engine and other utilities for interacting with the build process. This context is specific to the plugin and environment, allowing for environment-specific modifications without affecting the global context.
+   */
+  readonly environment: EnvironmentContext;
+}
+type BuildPluginContext<TResolvedConfig extends ResolvedConfig$1 = ResolvedConfig$1> = UnpluginBuildContext & PluginContext<TResolvedConfig>;
+type WithUnpluginBuildContext<TContext extends PluginContext> = UnpluginBuildContext & TContext;
+//#endregion
+//#region src/types/config.d.ts
+/**
+ * The {@link StormWorkspaceConfig | configuration} object for an entire Powerlines workspace
+ */
+type WorkspaceConfig = Partial<StormWorkspaceConfig> & Required<Pick<StormWorkspaceConfig, "workspaceRoot">>;
+type PluginFactory<in out TContext extends PluginContext = PluginContext, TOptions = any> = (options: TOptions) => MaybePromise<Plugin<TContext> | Plugin<TContext>[]>;
+/**
+ * A configuration tuple for a Powerlines plugin.
+ */
+type PluginConfigTuple<TContext extends PluginContext = PluginContext, TOptions = any> = [string | PluginFactory<TContext, TOptions>, TOptions] | [Plugin<TContext>];
+/**
+ * A configuration object for a Powerlines plugin.
+ */
+type PluginConfigObject<TContext extends PluginContext = PluginContext, TOptions = any> = {
+  plugin: string | PluginFactory<TContext, TOptions>;
+  options: TOptions;
+} | {
+  plugin: Plugin<TContext>;
+  options?: never;
+};
+/**
+ * A configuration tuple for a Powerlines plugin.
+ */
+type PluginConfig<TContext extends PluginContext = PluginContext> = string | PluginFactory<TContext, void> | Plugin<TContext> | PluginConfigTuple<TContext> | PluginConfigObject<TContext> | Promise<PluginConfig<TContext>> | PluginConfig<TContext>[];
+type PartialPlugin<TContext extends PluginContext = PluginContext> = DeepPartial<Plugin<TContext>>;
+type PartialPluginFactory<in out TContext extends PluginContext = PluginContext, TOptions = any> = (options: TOptions) => MaybePromise<PartialPlugin<TContext> | PartialPlugin<TContext>[]>;
+type ProjectType = "application" | "library";
+type Mode = "development" | "test" | "production";
+/**
+ * The configuration options for resolving modules in a Powerlines project.
+ */
+interface ResolveConfig {
+  /**
+   * List of fields in `package.json` to try when resolving a package's entry point. Note this takes lower precedence than conditional exports resolved from the exports field: if an entry point is successfully resolved from exports, the main field will be ignored.
+   *
+   * @defaultValue `["browser", "module", "jsnext:main", "jsnext"]`
+   *
+   * @see https://vite.dev/config/shared-options#resolve-mainfields
+   */
+  mainFields?: string[];
+  /**
+   * Array of strings indicating what conditions should be allowed when resolving [conditional exports](https://nodejs.org/api/packages.html#packages_conditional_exports) from a package.
+   *
+   * @defaultValue `["import", "require", "default"]`
+   *
+   * @see https://vite.dev/config/shared-options#resolve-conditions
+   */
+  conditions?: string[];
+  /**
+   * List of file extensions to try for imports that omit extensions. Note it is NOT recommended to omit extensions for custom import types (e.g. .vue) since it can interfere with IDE and type support.
+   *
+   * @defaultValue `[".mjs", ".js", ".mts", ".ts", ".jsx", ".tsx", ".json"]`
+   *
+   * @see https://vite.dev/config/shared-options#resolve-extensions
+   */
+  extensions?: string[];
+  /**
+   * Array of strings indicating what modules should be deduplicated to a single version in the build.
+   *
+   * @remarks
+   * This option is useful for ensuring that only one version of a module is included in the bundle, which can help reduce bundle size and avoid conflicts. If you have duplicated copies of the same dependency in your app (likely due to hoisting or linked packages in monorepos), use this option to force Powerlines to always resolve listed dependencies to the same copy (from project root).
+   *
+   * @see https://vite.dev/config/shared-options#resolve-dedupe
+   */
+  dedupe?: string[];
+  /**
+   * The alias mappings to use for module resolution during the build process.
+   *
+   * @remarks
+   * This option allows you to define custom path aliases for modules, which can be useful for simplifying imports and managing dependencies.
+   *
+   * @example
+   * ```ts
+   * {
+   *   alias: {
+   *     "@utils": "./src/utils",
+   *     "@components": "./src/components"
+   *   }
+   * }
+   * ```
+   *
+   * @see https://vite.dev/config/shared-options#resolve-alias
+   * @see https://github.com/rollup/plugins/tree/master/packages/alias
+   */
+  alias?: Record<string, string> | Array<{
+    find: string | RegExp;
+    replacement: string;
+  }>;
+  /**
+   * Enabling this setting causes Powerlines to determine file identity by the original file path (i.e. the path without following symlinks) instead of the real file path (i.e. the path after following symlinks).
+   *
+   * @defaultValue false
+   *
+   * @see https://esbuild.github.io/api/#preserve-symlinks
+   * @see https://rollupjs.org/configuration-options/#preservesymlinks
+   * @see https://webpack.js.org/configuration/resolve/#resolvesymlinks
+   * @see https://rolldown.rs/reference/InputOptions.resolve#symlinks
+   * @see https://vite.dev/config/shared-options#resolve-preservesymlinks
+   */
+  preserveSymlinks?: boolean;
+  /**
+   * A list of modules that should not be bundled, even if they are external dependencies.
+   *
+   * @remarks
+   * This option is useful for excluding specific modules from the bundle, such as Node.js built-in modules or other libraries that should not be bundled.
+   */
+  external?: (string | RegExp)[];
+  /**
+   * A list of modules that should always be bundled, even if they are external dependencies.
+   */
+  noExternal?: (string | RegExp)[];
+  /**
+   * Should the Powerlines CLI processes skip bundling the `node_modules` directory?
+   */
+  skipNodeModulesBundle?: boolean;
+}
+interface CopyConfig {
+  /**
+   * An optional path to a secondary/copied output directory for collecting distributable files prior to publishing/deployment.
+   *
+   * @remarks
+   * This option is useful when a separate directory is needed for collecting distributable files that are copied from the project, such as static assets or other non-code files. When using [Nx monorepo tools](https://nx.dev/), it is common for the {@link OutputConfig.path | project's output} to be copied to the `{workspaceRoot}/dist/{root}` directory, so that all of the monorepo's output is consolidated in a single location.
+   */
+  path: string;
+  /**
+   * A list of assets to copy to the output directory
+   *
+   * @remarks
+   * The assets can be specified as a string (path to the asset) or as an object with a `glob` property (to match multiple files). The paths are relative to the project root directory.
+   */
+  assets?: Array<string | AssetGlob>;
+}
+interface OutputConfig {
+  /**
+   * The output directory path for the project build.
+   *
+   * @remarks
+   * If a value is not provided, Powerlines will attempt to:
+   * 1. Use the `outDir` value in the `tsconfig.json` file.
+   * 2. Use the `dist` directory in the project root directory.
+   *
+   * @defaultValue "\{root\}/dist"
+   */
+  path?: string;
+  /**
+   * Configuration that specifies a secondary/copied output directory for potentially collecting distributable files prior to publishing/deployment.
+   *
+   * @remarks
+   * These options are useful when a separate directory is needed for collecting distributable files that are copied from the project, such as static assets or other non-code files. When using [Nx monorepo tools](https://nx.dev/), it is common for the {@link OutputConfig.path | project's output} to be copied to the `{workspaceRoot}/dist/{root}` directory, so that all of the monorepo's output is consolidated in a single location.
+   */
+  copy?: CopyConfig | false;
+  /**
+   * The folder where the generated runtime artifacts will be located
+   *
+   * @remarks
+   * This folder will contain all runtime artifacts and builtins generated during the "prepare" phase.
+   *
+   * @defaultValue "\{root\}/.powerlines"
+   */
+  artifactsPath?: string;
+  /**
+   * Should typescript declaration modules be generated during the build for the project?
+   */
+  dts?: boolean;
+  /**
+   * The path of the generated runtime types declaration file relative to the workspace root.
+   *
+   * @remarks
+   * This value will be set to `true` automatically when {@link OutputConfig.dts | dts} is set to `true`.
+   *
+   * @defaultValue "\{root\}/powerlines.d.ts"
+   */
+  types?: string | false;
+  /**
+   * The module format of the output files
+   *
+   * @remarks
+   * This option can be a single format or an array of formats. If an array is provided, multiple builds will be generated for each format.
+   *
+   * @defaultValue "esm"
+   */
+  format?: Format | Format[];
+  /**
+   * Generate source maps for the output files
+   *
+   * @remarks
+   * This option can be a boolean or a string specifying the type of source map to generate. If set to `true`, external source maps will be generated. If set to `"inline"`, source maps will be included in the output files as data URIs. If set to `"hidden"`, external source maps will be generated but not referenced in the output files.
+   */
+  sourceMap?: boolean | "inline" | "hidden";
+  /**
+   * Minify the output files
+   *
+   * @remarks
+   * This option can be a boolean or a string specifying the type of minification to apply. If set to `true`, the output files will be minified. If set to `"terser"`, the Terser minifier will be used. If set to `"esbuild"`, the esbuild minifier will be used.
+   *
+   * @defaultValue false
+   */
+  minify?: boolean;
+  /**
+   * Control whether built-in Node.js module imports use the `node:` protocol.
+   *
+   * @remarks
+   * If no option is provided, built-in module imports are not transformed. The following options are available for this setting:
+   * - `true`: Add the node: prefix to built-in module imports.
+   * - `"strip"`: Remove the node: prefix from built-in module imports.
+   *
+   * @see https://tsdown.dev/reference/api/Interface.InlineConfig#nodeprotocol
+   * @see https://nodejs.org/api/esm.html#node-imports
+   */
+  nodeProtocol?: "strip" | true;
+  /**
+   * Whether to overwrite previously generated files in the artifacts directory during the build process.
+   *
+   * @remarks
+   * When set to `true`, Powerlines will overwrite any existing files in the artifacts directory with the newly generated files during the build process. When set to `false`, Powerlines will skip generating files that already exist in the artifacts directory, which can help speed up the build process by avoiding unnecessary file writes. This option is only relevant when the {@link OutputConfig.storage | storage option} is configured to use an adapter that writes files to the local file system. If using a `virtual` storage adapter, this option has no effect.
+   *
+   * @defaultValue true
+   */
+  overwrite?: boolean;
+  /**
+   * A string preset or a custom {@link StoragePort} to provide fine-grained control over generated/output file storage.
+   *
+   * @remarks
+   * If a string preset is provided, it must be one of the following values:
+   * - `"fs"`: Uses the local file system for storage.
+   * - `"virtual"`: Uses an in-memory virtual file system for storage.
+   *
+   * If a custom {@link StoragePort} is provided, it will be used for all file storage operations during the build process.
+   *
+   * @defaultValue "virtual"
+   */
+  storage?: StoragePort | StoragePreset;
+}
+interface FrameworkOptions {
+  /**
+   * The name of the framework
+   *
+   * @remarks
+   * This value is used to identify the framework in logs, error messages, and other places where the framework's name is needed.
+   *
+   * @defaultValue "powerlines"
+   */
+  name: string;
+  /**
+   * The version of the framework
+   *
+   * @remarks
+   * This value is used to identify the version of the framework in logs, error messages, and other places where the framework's version is needed.
+   *
+   * @defaultValue "0.0.1"
+   */
+  version?: string;
+  /**
+   * The organization or author of the framework
+   *
+   * @defaultValue "storm-software"
+   */
+  orgId: string;
+}
+interface Options {
+  /**
+   * The current working directory the Powerlines processes should operate in
+   *
+   * @remarks
+   * If not provided, the {@link WorkspaceConfig.workspaceRoot | workspace root} will be used as the current working directory. If the workspace root cannot be determined, the process's current working directory will be used.
+   */
+  cwd?: string;
+  /**
+   * The log level label indicating the severity of the log message, or a more detailed log level configuration object that allows for specifying different log levels for different categories of logs.
+   *
+   * @remarks
+   * The log level determines the minimum severity of messages that will be logged. For example, if the log level is set to `LogLevel.INFO`, then messages with a severity of `INFO`, `WARN`, and `ERROR` will be logged, while messages with a severity of `DEBUG` and `TRACE` will be ignored. Setting the log level to `LogLevel.SILENT` will disable all logging. Alternatively, you can provide a more detailed configuration object that allows you to specify different log levels for different categories of logs, providing granular control over the logging behavior for different aspects of the system.
+   *
+   * @defaultValue "info"
+   */
+  logLevel?: LogLevelUserConfig;
+  /**
+   * Details about the framework being used in the current execution, which can be used by plugins and other parts of the system to customize behavior based on the framework.
+   */
+  framework?: FrameworkOptions;
+}
+interface BaseExecutionOptions extends RequiredKeys<Options, "cwd"> {
+  /**
+   * The root directory of the project
+   */
+  root: string;
+}
+interface ExecutionOptions extends BaseExecutionOptions {
+  /**
+   * A unique identifier for the current execution instance, which can be used for logging and other purposes to distinguish between different executions in the same process.
+   */
+  executionId?: string;
+  /**
+   * The index of the current execution instance among all configured instances in the Powerlines process
+   */
+  configIndex?: number;
+  /**
+   * A path to a custom configuration file to be used instead of the default `powerlines.json`, `powerlines.config.js`, or `powerlines.config.ts` files.
+   *
+   * @remarks
+   * This option is useful for running Powerlines commands with different configuration files, such as in CI/CD environments or when testing different configurations.
+   */
+  configFile: string;
+  /**
+   * A logging function provided by the code invoking the Powerlines execution process, which can be used for logging messages during the build process instead of the default Powerlines logger.
+   *
+   * @remarks
+   * Providing a custom logging function allows you to integrate Powerlines logging with your own logging system or to customize the logging behavior, such as formatting log messages differently or sending logs to an external service. If a custom logging function is not provided, Powerlines will use its default logger implementation.
+   *
+   * @important
+   * This function cannot be provided by the Powerlines engine, as it is not serializable. It must be passed directly to the execution context when creating it, and will not be preserved if the context is cloned or serialized.
+   */
+  logFn?: LogFn;
+}
+interface Config {
+  /**
+   * Defines entries and location(s) of entry modules for the bundle. Relative paths are resolved based on the `root` option.
+   */
+  input?: FileReferenceInput | FileReferenceInput[] | Record<string, FileReferenceInput | FileReferenceInput[]>;
+  /**
+   * Configuration for the output files generated by processing the source code
+   */
+  output?: OutputConfig;
+  /**
+   * The date to use for compatibility checks
+   *
+   * @remarks
+   * This date can be used by plugins and build processes to determine compatibility with certain features or APIs. It is recommended to set this date to the date when the project was last known to be compatible with the desired features or APIs. If no value is provided, the latest compatibility date will be used.
+   *
+   * @see https://developers.cloudflare.com/pages/platform/compatibility-dates/
+   * @see https://docs.netlify.com/configure-builds/get-started/#set-a-compatibility-date
+   * @see https://github.com/unjs/compatx
+   */
+  compatibilityDate?: CompatibilityDateSpec;
+  /**
+   * The log level label indicating the severity of the log message, or a more detailed log level configuration object that allows for specifying different log levels for different categories of logs.
+   *
+   * @remarks
+   * The log level determines the minimum severity of messages that will be logged. For example, if the log level is set to `LogLevel.INFO`, then messages with a severity of `INFO`, `WARN`, and `ERROR` will be logged, while messages with a severity of `DEBUG` and `TRACE` will be ignored. Setting the log level to `LogLevel.SILENT` will disable all logging. Alternatively, you can provide a more detailed configuration object that allows you to specify different log levels for different categories of logs, providing granular control over the logging behavior for different aspects of the system.
+   *
+   * @defaultValue "info"
+   */
+  logLevel?: LogLevelUserConfig;
+  /**
+   * Configuration for module resolution during processing of the source code
+   */
+  resolve?: ResolveConfig;
+  /**
+   * The platform to build the project for
+   *
+   * @defaultValue "neutral"
+   */
+  platform?: "node" | "browser" | "neutral";
+  /**
+   * Define global constant replacements. Entries will be defined as globals during dev and statically replaced during build.
+   *
+   * @remarks
+   * This option allows you to specify global constants that will be replaced in the code during the build process. It is similar to the `define` option in esbuild and Vite, enabling you to replace specific identifiers with constant expressions at build time.
+   *
+   * @example
+   * ```ts
+   * {
+   *   define: {
+   *     __VERSION__: '"1.0.0"',
+   *     __DEV__: 'process.env.NODE_ENV !== "production"'
+   *   }
+   * }
+   * ```
+   *
+   * @see https://esbuild.github.io/api/#define
+   * @see https://vitejs.dev/config/build-options.html#define
+   * @see https://github.com/rollup/plugins/tree/master/packages/replace
+   */
+  define?: Record<string, any>;
+  /**
+   * Global variables that will have import statements injected where necessary
+   *
+   * @remarks
+   * This option allows you to specify global variables that should be automatically imported from specified modules whenever they are used in the code. This is particularly useful for polyfilling Node.js globals in a browser environment.
+   *
+   * @example
+   * ```ts
+   * {
+   *   inject: {
+   *     process: 'process/browser',
+   *     Buffer: ['buffer', 'Buffer'],
+   *   }
+   * }
+   * ```
+   *
+   * @see https://github.com/rollup/plugins/tree/master/packages/inject
+   */
+  inject?: Record<string, string | string[]>;
+  /**
+   * The path to the tsconfig file to be used by the compiler
+   *
+   * @remarks
+   * If a value is not provided, the plugin will attempt to find the `tsconfig.json` file in the project root directory. The parsed tsconfig compiler options will be merged with the {@link Options.tsconfigRaw} value (if provided).
+   *
+   * @defaultValue "\{projectRoot\}/tsconfig.json"
+   */
+  tsconfig?: string;
+  /**
+   * The raw {@link TSConfig} object to be used by the compiler. This object will be merged with the `tsconfig.json` file.
+   *
+   * @see https://www.typescriptlang.org/tsconfig
+   *
+   * @remarks
+   * If populated, this option takes higher priority than `tsconfig`
+   */
+  tsconfigRaw?: TSConfig;
+}
+interface EnvironmentConfig extends Config {
+  /**
+   * Configuration options for the preview server
+   */
+  preview?: PreviewOptions;
+  /**
+   * A flag indicating whether the build is for a Server-Side Rendering environment.
+   */
+  ssr?: boolean;
+  /**
+   * The runtime environment for the build, which can be used by plugins to determine how to process the source code and generate runtime artifacts.
+   *
+   * @remarks
+   * This option can be used to specify the target runtime environment for the build, such as "nodejs", "browser", "workerd", or "edge". Plugins can use this information to determine how to process the source code and generate runtime artifacts that are compatible with the specified environment. If no value is provided, plugins will need to determine the runtime environment based on other factors, such as the presence of certain dependencies or configuration options.
+   */
+  runtime?: "nodejs" | "browser" | "workerd" | "edge";
+  /**
+   * Define if this environment is used for Server-Side Rendering
+   *
+   * @defaultValue "server" (if it isn't the client environment)
+   */
+  consumer?: "client" | "server";
+}
+interface UserConfig extends Config {
+  /**
+   * The name of the project
+   */
+  name?: string;
+  /**
+   * The project display title
+   *
+   * @remarks
+   * This option is used in documentation generation and other places where a human-readable title is needed.
+   */
+  title?: string;
+  /**
+   * A description of the project
+   *
+   * @remarks
+   * If this option is not provided, the build process will try to use the \`description\` value from the `\package.json\` file.
+   */
+  description?: string;
+  /**
+   * The organization or author of the project
+   *
+   * @remarks
+   * If this option is not provided, the build process will try to use the \`author\` value from the \`package.json\` file. If the \`author\` value cannot be determined, the {@link name | name configuration} will be used.
+   */
+  organization?: string;
+  /**
+   * Explicitly set a mode to run in. This mode will be used at various points throughout the Powerlines processes, such as when compiling the source code.
+   *
+   * @defaultValue "production"
+   */
+  mode?: Mode;
+  /**
+   * The type of project being built
+   *
+   * @defaultValue "application"
+   */
+  projectType?: ProjectType;
+  /**
+   * Should the Powerlines processes automatically install missing package dependencies?
+   *
+   * @remarks
+   * When set to `true`, Powerlines will attempt to install any missing dependencies using the package manager detected in the project (e.g., npm, yarn, pnpm). This can be useful for ensuring that all required packages are available during the build and preparation phases.
+   *
+   * @defaultValue false
+   */
+  autoInstall?: boolean;
+  /**
+   * Should the compiler processes skip any improvements that make use of cache?
+   *
+   * @defaultValue false
+   */
+  skipCache?: boolean;
+  /**
+   * A list of resolvable paths to plugins used during the build process
+   */
+  plugins?: PluginConfig<any>[];
+  /**
+   * Environment-specific configurations
+   */
+  environments?: Record<string, EnvironmentConfig>;
+  /**
+   * Should a single `build` process be ran for each environment?
+   *
+   * @remarks
+   * This option determines how environments are managed during the `build` process. The available options are:
+   *
+   * - `false`: A separate build is ran for each environment.
+   * - `true`: A single build is ran for all environments.
+   *
+   * @defaultValue false
+   */
+  singleBuild?: boolean;
+}
+type ConfigParams = BaseExecutionOptions & Pick<Required<UserConfig>, "mode"> & {
+  /**
+   * A string identifier for the Powerlines command being executed
+   */
+  command: string;
+};
+type UserConfigFnObject = (env: ConfigParams) => UserConfig | UserConfig[];
+type UserConfigFnPromise = (env: ConfigParams) => Promise<UserConfig | UserConfig[]>;
+type UserConfigFn = (env: ConfigParams) => UserConfig | UserConfig[] | Promise<UserConfig | UserConfig[]>;
+type UserConfigExport = UserConfig | UserConfig[] | Promise<UserConfig | UserConfig[]> | UserConfigFnObject | UserConfigFnPromise | UserConfigFn;
+type ParsedUserConfig = ResolvedConfig<UserConfig> & {
+  /**
+   * The path to the user configuration file, if it exists.
+   *
+   * @remarks
+   * This is typically the `powerlines.json`, `powerlines.config.js`, or `powerlines.config.ts` file in the project root.
+   */
+  configFile?: ConfigLayer<UserConfig>["configFile"];
+};
+type InlineConfigPaths = {
+  /**
+   * The root directory of the project
+   */
+  root: string;
+  /**
+   * A path to a custom configuration file to be used instead of the default `powerlines.json`, `powerlines.config.js`, or `powerlines.config.ts` files.
+   *
+   * @remarks
+   * This option is useful for running Powerlines commands with different configuration files, such as in CI/CD environments or when testing different configurations.
+   */
+  configFile?: string;
+} | {
+  /**
+   * The root directory of the project
+   */
+  root?: string;
+  /**
+   * A path to a custom configuration file to be used instead of the default `powerlines.json`, `powerlines.config.js`, or `powerlines.config.ts` files.
+   *
+   * @remarks
+   * This option is useful for running Powerlines commands with different configuration files, such as in CI/CD environments or when testing different configurations.
+   */
+  configFile?: string;
+};
+/**
+ * The configuration provided while executing Powerlines commands.
+ */
+type InlineConfig<TUserConfig extends UserConfig = UserConfig> = DeepPartial<TUserConfig> & {
+  /**
+   * The root directory of the project
+   */
+  root?: string;
+  /**
+   * A path to a custom configuration file to be used instead of the default `powerlines.json`, `powerlines.config.js`, or `powerlines.config.ts` files.
+   *
+   * @remarks
+   * This option is useful for running Powerlines commands with different configuration files, such as in CI/CD environments or when testing different configurations.
+   */
+  configFile?: string;
+  /**
+   * A string identifier for the Powerlines command being executed
+   */
+  command: string;
+  /**
+   * Additional arguments provided during execution of the command, such as CLI flags or other parameters that may be relevant to the command being executed.
+   */
+  additionalArgs?: Record<string, string | string[]>;
+  /**
+   * Details about the framework being used in the current execution, which can be used by plugins and other parts of the system to customize behavior based on the framework.
+   *
+   * @remarks
+   * This should only be used by framework plugins to ensure the correct framework name is applied
+   *
+   * @internal
+   */
+  framework?: FrameworkOptions;
+};
+type CreateInlineConfig<TUserConfig extends UserConfig = UserConfig> = RequiredKeys<InlineConfig<TUserConfig>, "root"> & {
+  /**
+   * The package name (from the \`package.json\`) for the project that will be used in the \`create\` command to create a new project based on this configuration
+   */
+  packageName?: string;
+};
+type CleanInlineConfig<TUserConfig extends UserConfig = UserConfig> = InlineConfig<TUserConfig>;
+type PrepareInlineConfig<TUserConfig extends UserConfig = UserConfig> = InlineConfig<TUserConfig>;
+type TypesInlineConfig<TUserConfig extends UserConfig = UserConfig> = InlineConfig<TUserConfig>;
+type BuildInlineConfig<TUserConfig extends UserConfig = UserConfig> = InlineConfig<TUserConfig>;
+type LintInlineConfig<TUserConfig extends UserConfig = UserConfig> = InlineConfig<TUserConfig>;
+type TestInlineConfig<TUserConfig extends UserConfig = UserConfig> = InlineConfig<TUserConfig>;
+type DocsInlineConfig<TUserConfig extends UserConfig = UserConfig> = InlineConfig<TUserConfig>;
+type DeployInlineConfig<TUserConfig extends UserConfig = UserConfig> = InlineConfig<TUserConfig>;
+interface ResolvedEntryFileReference extends FileReference {
+  /**
+   * The user provided entry point in the source code
+   */
+  input?: FileReference;
+  /**
+   * An optional name to use in the package export during the build process
+   */
+  output?: string;
+}
+type ResolvedEnvironmentConfig = RequiredKeys<Omit<EnvironmentConfig, "preview">, "input" | "consumer" | "ssr"> & {
+  /**
+   * A string identifier for the environment used by the system and plugins to determine which environment-specific configuration to use during the build process.
+   */
+  id: string;
+  /**
+   * The name of the environment provided by the user in the {@link UserConfig.environments | environments} configuration.
+   */
+  name: string;
+  /**
+   * Configuration options for the preview server
+   */
+  preview?: ResolvedPreviewOptions;
+};
+/**
+ * The configuration options for resolving modules in a Powerlines project.
+ */
+type ResolvedResolveConfig = Required<Omit<ResolveConfig, "external" | "noExternal">> & {
+  /**
+   * A list of modules that should not be bundled, even if they are external dependencies.
+   *
+   * @remarks
+   * This option is useful for excluding specific modules from the bundle, such as Node.js built-in modules or other libraries that should not be bundled.
+   */
+  external?: string[];
+  /**
+   * A list of modules that should always be bundled, even if they are external dependencies.
+   */
+  noExternal?: string[];
+};
+type ResolvedAssetGlob = AssetGlob & Required<Pick<AssetGlob, "input">>;
+type ResolvedCopyConfig = Required<Omit<CopyConfig, "assets">> & {
+  assets: ResolvedAssetGlob[];
+};
+type ResolvedOutputConfig = Required<Omit<OutputConfig, "copy" | "storage">> & Pick<OutputConfig, "storage"> & {
+  copy: ResolvedCopyConfig | false;
+};
+/**
+ * The base resolved configuration options for a Powerlines project, after being processed and normalized by the configuration loading process.
+ */
+type ResolvedConfig$1<TUserConfig extends UserConfig = UserConfig, TExecutionOptions extends ExecutionOptions = ExecutionOptions> = Omit<TExecutionOptions, "logLevel"> & Omit<RequiredKeys<TUserConfig, "input" | "name" | "title" | "plugins" | "mode" | "input" | "tsconfig" | "platform" | "projectType">, "compatibilityDate" | "output" | "resolve" | "logLevel" | "environments"> & {
+  /**
+   * The configuration options read from a configuration file on disk, which may be used to resolve the final configuration for the context. This typically includes the user configuration options defined in the `powerlines.config.ts` file, as well as any inline configuration options provided during execution.
+   */
+  readonly userConfig: DeepReadonly<TUserConfig>;
+  /**
+   * The configuration options provided by plugins added by the user (and other plugins)
+   */
+  readonly inlineConfig: DeepReadonly<InlineConfig<TUserConfig>>;
+  /**
+   * The configuration options that were provided by Powerlines plugins, which may have been merged with the user configuration and modified by the configuration loading process.
+   */
+  readonly pluginConfig: DeepReadonly<DeepPartial<TUserConfig>>;
+  /**
+   * A string identifier for the Powerlines command being executed.
+   */
+  readonly command: NonUndefined<InlineConfig<TUserConfig>["command"]>;
+  /**
+   * A path to a custom configuration file to be used instead of the default `powerlines.json`, `powerlines.config.js`, or `powerlines.config.ts` files.
+   *
+   * @remarks
+   * This option is useful for running Powerlines commands with different configuration files, such as in CI/CD environments or when testing different configurations.
+   */
+  readonly configFile: string;
+  /**
+   * The output configuration options to use for the build process
+   */
+  output: ResolvedOutputConfig;
+  /**
+   * Configuration for module resolution during processing of the source code
+   */
+  resolve: ResolvedResolveConfig;
+  /**
+   * The date to use for compatibility checks
+   *
+   * @remarks
+   * This date can be used by plugins and build processes to determine compatibility with certain features or APIs. It is recommended to set this date to the date when the project was last known to be compatible with the desired features or APIs.
+   *
+   * @see https://developers.cloudflare.com/pages/platform/compatibility-dates/
+   * @see https://docs.netlify.com/configure-builds/get-started/#set-a-compatibility-date
+   * @see https://github.com/unjs/compatx
+   */
+  compatibilityDate: CompatibilityDates;
+  /**
+   * The log level label indicating the severity of the log message, or a more detailed log level configuration object that allows for specifying different log levels for different categories of logs.
+   *
+   * @remarks
+   * The log level determines the minimum severity of messages that will be logged. For example, if the log level is set to `LogLevel.INFO`, then messages with a severity of `INFO`, `WARN`, and `ERROR` will be logged, while messages with a severity of `DEBUG` and `TRACE` will be ignored. Setting the log level to `LogLevel.SILENT` will disable all logging. Alternatively, you can provide a more detailed configuration object that allows you to specify different log levels for different categories of logs, providing granular control over the logging behavior for different aspects of the system.
+   */
+  logLevel: LogLevelResolvedConfig;
+  /**
+   * Environment-specific configurations
+   */
+  environments: Record<string, ResolvedEnvironmentConfig>;
+};
+type InferOverridableConfig<TResolvedConfig extends ResolvedConfig$1 = ResolvedConfig$1> = DeepPartial<Omit<TResolvedConfig, "userConfig" | "inlineConfig" | "pluginConfig" | "cwd" | "configFile" | "command">>;
+/**
+ * The resolved configuration options for a Powerlines environment, after being processed and normalized by the configuration loading process.
+ */
+type EnvironmentResolvedConfig<TResolvedConfig extends ResolvedConfig$1 = ResolvedConfig$1> = TResolvedConfig & {
+  /**
+   * The configuration provided when initializing the Powerlines API.
+   *
+   * @remarks
+   * This configuration is used during the initialization of the Powerlines API.
+   */
+  readonly environmentConfig: DeepReadonly<EnvironmentConfig>;
+  /**
+   * The resolved configuration options for the environment, which may include additional properties or modifications made during the configuration loading process.
+   */
+  environment: ResolvedEnvironmentConfig;
+};
+//#endregion
+export { ExecutionContext as $, PluginHook as $t, ResolveConfig as A, LogLevelUserConfig as At, UserConfig as B, HooksList as Bt, PartialPluginFactory as C, VirtualFileSystemInterface as Cn, CustomLoggerMessage as Ct, PluginFactory as D, LogFnOptions as Dt, PluginConfigTuple as E, LogFnMeta as Et, ResolvedEnvironmentConfig as F, LoggerMeta as Ft, WorkspaceConfig as G, InferHookThisType as Gt, UserConfigFn as H, InferHookFunction as Ht, ResolvedOutputConfig as I, LoggerOptions as It, Context as J, TransformHookFilter as Jt, BaseContext as K, NormalizedStringFilter as Kt, ResolvedResolveConfig as L, PowerlinesMessage as Lt, ResolvedConfig$1 as M, LogMeta as Mt, ResolvedCopyConfig as N, Logger as Nt, PrepareInlineConfig as O, LogLevel as Ot, ResolvedEntryFileReference as P, LoggerMessage as Pt, EnvironmentPlugin as Q, Plugin as Qt, TestInlineConfig as R, CallHookOptions as Rt, PartialPlugin as S, VirtualFileMetadata as Sn, CustomLogger as St, PluginConfigObject as T, WriteOptions as Tn, LogFn as Tt, UserConfigFnObject as U, InferHookParameters as Ut, UserConfigExport as V, HooksListItem as Vt, UserConfigFnPromise as W, InferHookReturnType as Wt, EmitOptions as X, HookFunctions as Xt, EmitEntryOptions as Y, BasePlugin as Yt, EnvironmentContext as Z, Hooks as Zt, LintInlineConfig as _, StoragePort as _n, ParsedTypeScriptConfig as _t, ConfigParams as a, BuilderVariant as an, ResolveResult as at, OutputConfig as b, VirtualFileData as bn, TSCompilerOptions as bt, DeployInlineConfig as c, UnpluginOptions$1 as cn, SelectHookResultItem as ct, EnvironmentResolvedConfig as d, CommandType as dn, TransformResult$1 as dt, PluginHookFields as en, FetchOptions as et, ExecutionOptions as f, Commands as fn, UnimportContext as ft, InlineConfigPaths as g, StorageAdapter as gn, Level as gt, InlineConfig as h, ResolveOptions$1 as hn, DeepkitOptions as ht, Config as i, TypesResult as in, PluginContext as it, ResolvedAssetGlob as j, LogMessage as jt, ProjectType as k, LogLevelResolvedConfig as kt, DocsInlineConfig as l, BaseCommandType as ln, SelectHooksOptions as lt, InferOverridableConfig as m, SupportedCommands as mn, WithUnpluginBuildContext as mt, BuildInlineConfig as n, PluginHooks as nn, MetaInfo as nt, CopyConfig as o, UnpluginBuilderVariant as on, Resolver as ot, FrameworkOptions as p, ExecutionApiMethods as pn, UnresolvedContext as pt, BuildPluginContext as q, PluginFilter as qt, CleanInlineConfig as r, PluginNonHookFields as rn, ParseOptions as rt, CreateInlineConfig as s, UnpluginHookFunctions as sn, SelectHookResult as st, BaseExecutionOptions as t, PluginHookObject as tn, InitContextOptions as tt, EnvironmentConfig as u, BaseExecutionApiMethods as un, SourceFile as ut, Mode as v, StoragePreset as vn, RawReflectionMode as vt, PluginConfig as w, WriteData as wn, LogCategory as wt, ParsedUserConfig as x, VirtualFileExtension as xn, TSConfig as xt, Options as y, VirtualFile as yn, ReflectionMode as yt, TypesInlineConfig as z, HookListOrders as zt };
+//# sourceMappingURL=config-BnV_o0Es.d.cts.map