@powerlines/plugin-alloy 0.16.0 → 0.16.2

package/dist/_virtual/rolldown_runtime.mjs

@@ -1,29 +0,0 @@
-//#region rolldown:runtime
-var __defProp = Object.defineProperty;
-var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
-var __getOwnPropNames = Object.getOwnPropertyNames;
-var __hasOwnProp = Object.prototype.hasOwnProperty;
-var __copyProps = (to, from, except, desc) => {
-	if (from && typeof from === "object" || typeof from === "function") {
-		for (var keys = __getOwnPropNames(from), i = 0, n = keys.length, key; i < n; i++) {
-			key = keys[i];
-			if (!__hasOwnProp.call(to, key) && key !== except) {
-				__defProp(to, key, {
-					get: ((k) => from[k]).bind(null, key),
-					enumerable: !(desc = __getOwnPropDesc(from, key)) || desc.enumerable
-				});
-			}
-		}
-	}
-	return to;
-};
-var __reExport = (target, mod, secondTarget, symbols) => {
-	if (symbols) {
-		__defProp(target, Symbol.toStringTag, { value: "Module" });
-		secondTarget && __defProp(secondTarget, Symbol.toStringTag, { value: "Module" });
-	}
-	__copyProps(target, mod, "default"), secondTarget && __copyProps(secondTarget, mod, "default");
-};
-
-//#endregion
-export { __reExport };

package/dist/powerlines/src/lib/utilities/file-header.cjs

@@ -1,13 +0,0 @@
-const require_rolldown_runtime = require('../../../../_virtual/rolldown_runtime.cjs');
-let __stryke_string_format_title_case = require("@stryke/string-format/title-case");
-
-//#region ../powerlines/src/lib/utilities/file-header.ts
-function getBaseFileHeader(context) {
-	return `
-// Generated with ${(0, __stryke_string_format_title_case.titleCase)(context.config.framework)}
-// Note: Do not edit this file manually - it will be overwritten automatically
-`;
-}
-
-//#endregion
-exports.getBaseFileHeader = getBaseFileHeader;

package/dist/powerlines/src/lib/utilities/file-header.mjs

@@ -1,12 +0,0 @@
-import { titleCase } from "@stryke/string-format/title-case";
-
-//#region ../powerlines/src/lib/utilities/file-header.ts
-function getBaseFileHeader(context) {
-	return `
-// Generated with ${titleCase(context.config.framework)}
-// Note: Do not edit this file manually - it will be overwritten automatically
-`;
-}
-
-//#endregion
-export { getBaseFileHeader };

package/dist/powerlines/src/types/babel.d.mts

@@ -1,2 +0,0 @@
-import "./config.mjs";
-import "./context.mjs";

package/dist/powerlines/src/types/build.d.cts

@@ -1,145 +0,0 @@
-//#region ../powerlines/src/types/build.d.ts
-
-type UnpluginBuildVariant = "rollup" | "webpack" | "rspack" | "vite" | "esbuild" | "farm" | "unloader" | "rolldown";
-interface BuildConfig {
-  /**
-   * The platform to build the project for
-   *
-   * @defaultValue "neutral"
-   */
-  platform?: "node" | "browser" | "neutral";
-  /**
-   * Array of strings indicating the polyfills to include for the build.
-   *
-   * @remarks
-   * This option allows you to specify which polyfills should be included in the build process to ensure compatibility with the target environment. The paths for the polyfills can use placeholder tokens (the `replacePathTokens` helper function will be used to resolve the actual values).
-   *
-   * @example
-   * ```ts
-   * {
-   *   polyfill: ['{projectRoot}/custom-polyfill.ts']
-   * }
-   * ```
-   */
-  polyfill?: string[];
-  /**
-   * Array of strings indicating the order in which fields in a package.json file should be resolved to determine the entry point for a module.
-   *
-   * @defaultValue `['browser', 'module', 'jsnext:main', 'jsnext']`
-   */
-  mainFields?: string[];
-  /**
-   * Array of strings indicating what conditions should be used for module resolution.
-   */
-  conditions?: string[];
-  /**
-   * Array of strings indicating what file extensions should be used for module resolution.
-   *
-   * @defaultValue `['.mjs', '.js', '.mts', '.ts', '.jsx', '.tsx', '.json']`
-   */
-  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.
-   */
-  dedupe?: string[];
-  /**
-   * Array of strings or regular expressions that indicate what modules are builtin for the environment.
-   */
-  builtins?: (string | RegExp)[];
-  /**
-   * Define global variable replacements.
-   *
-   * @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 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://github.com/rollup/plugins/tree/master/packages/alias
-   */
-  alias?: Record<string, string> | Array<{
-    find: string | RegExp;
-    replacement: string;
-  }>;
-  /**
-   * 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;
-  /**
-   * If true, `process.env` referenced in code will be preserved as-is and evaluated in runtime. Otherwise, it is statically replaced as an empty object.
-   *
-   * @defaultValue false
-   */
-  keepProcessEnv?: boolean;
-  /**
-   * An optional set of override options to apply to the selected build variant.
-   *
-   * @remarks
-   * This option allows you to provide configuration options with the guarantee that they will **not** be overridden and will take precedence over other build configurations.
-   */
-  override?: Record<string, any>;
-}
-type BuildResolvedConfig = Omit<BuildConfig, "override">;
-//#endregion
-export { BuildConfig, BuildResolvedConfig, UnpluginBuildVariant };

package/dist/powerlines/src/types/build.d.mts

@@ -1,145 +0,0 @@
-//#region ../powerlines/src/types/build.d.ts
-
-type UnpluginBuildVariant = "rollup" | "webpack" | "rspack" | "vite" | "esbuild" | "farm" | "unloader" | "rolldown";
-interface BuildConfig {
-  /**
-   * The platform to build the project for
-   *
-   * @defaultValue "neutral"
-   */
-  platform?: "node" | "browser" | "neutral";
-  /**
-   * Array of strings indicating the polyfills to include for the build.
-   *
-   * @remarks
-   * This option allows you to specify which polyfills should be included in the build process to ensure compatibility with the target environment. The paths for the polyfills can use placeholder tokens (the `replacePathTokens` helper function will be used to resolve the actual values).
-   *
-   * @example
-   * ```ts
-   * {
-   *   polyfill: ['{projectRoot}/custom-polyfill.ts']
-   * }
-   * ```
-   */
-  polyfill?: string[];
-  /**
-   * Array of strings indicating the order in which fields in a package.json file should be resolved to determine the entry point for a module.
-   *
-   * @defaultValue `['browser', 'module', 'jsnext:main', 'jsnext']`
-   */
-  mainFields?: string[];
-  /**
-   * Array of strings indicating what conditions should be used for module resolution.
-   */
-  conditions?: string[];
-  /**
-   * Array of strings indicating what file extensions should be used for module resolution.
-   *
-   * @defaultValue `['.mjs', '.js', '.mts', '.ts', '.jsx', '.tsx', '.json']`
-   */
-  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.
-   */
-  dedupe?: string[];
-  /**
-   * Array of strings or regular expressions that indicate what modules are builtin for the environment.
-   */
-  builtins?: (string | RegExp)[];
-  /**
-   * Define global variable replacements.
-   *
-   * @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 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://github.com/rollup/plugins/tree/master/packages/alias
-   */
-  alias?: Record<string, string> | Array<{
-    find: string | RegExp;
-    replacement: string;
-  }>;
-  /**
-   * 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;
-  /**
-   * If true, `process.env` referenced in code will be preserved as-is and evaluated in runtime. Otherwise, it is statically replaced as an empty object.
-   *
-   * @defaultValue false
-   */
-  keepProcessEnv?: boolean;
-  /**
-   * An optional set of override options to apply to the selected build variant.
-   *
-   * @remarks
-   * This option allows you to provide configuration options with the guarantee that they will **not** be overridden and will take precedence over other build configurations.
-   */
-  override?: Record<string, any>;
-}
-type BuildResolvedConfig = Omit<BuildConfig, "override">;
-//#endregion
-export { BuildConfig, BuildResolvedConfig, UnpluginBuildVariant };

package/dist/powerlines/src/types/commands.d.cts

@@ -1,8 +0,0 @@
-import { MaybePromise } from "@stryke/types/base";
-import { ArrayValues } from "@stryke/types/array";
-
-//#region ../powerlines/src/types/commands.d.ts
-declare const SUPPORTED_COMMANDS: readonly ["new", "clean", "prepare", "lint", "test", "build", "docs", "deploy", "finalize"];
-type CommandType = ArrayValues<typeof SUPPORTED_COMMANDS>;
-//#endregion
-export { CommandType };

package/dist/powerlines/src/types/commands.d.mts

@@ -1,9 +0,0 @@
-import "./context.mjs";
-import { MaybePromise } from "@stryke/types/base";
-import { ArrayValues } from "@stryke/types/array";
-
-//#region ../powerlines/src/types/commands.d.ts
-declare const SUPPORTED_COMMANDS: readonly ["new", "clean", "prepare", "lint", "test", "build", "docs", "deploy", "finalize"];
-type CommandType = ArrayValues<typeof SUPPORTED_COMMANDS>;
-//#endregion
-export { CommandType };