@powerlines/plugin-date 0.12.259 → 0.12.261

package/dist/packages/deepkit/src/types.d.mts

@@ -1,10 +0,0 @@
-import { SerializedTypes } from "../schemas/reflection.mjs";
-import { ReflectionClass } from "@powerlines/deepkit/vendor/type";
-
-//#region ../deepkit/src/types.d.ts
-type Reflection<T extends Record<string, any> = Record<string, any>> = ReflectionClass<T> & {
-  dataBuffer?: ArrayBuffer;
-  messageRoot?: SerializedTypes;
-};
-//#endregion
-export { Reflection };

package/dist/packages/plugin-alloy/src/types/plugin.d.mts

@@ -1,36 +0,0 @@
-import { PluginContext } from "../../../powerlines/src/types/context.mjs";
-import { BabelPluginResolvedConfig, BabelPluginUserConfig } from "../../../plugin-babel/src/types/plugin.mjs";
-import { Children, PrintTreeOptions } from "@alloy-js/core";
-
-//#region ../plugin-alloy/src/types/plugin.d.ts
-type AlloyPluginOptions = Partial<PrintTreeOptions> & {
-  /**
-   * If true, the Alloy framework is used to generate Typescript output files.
-   *
-   * @defaultValue true
-   */
-  typescript?: boolean;
-  /**
-   * If true, the Alloy framework is used to generate JSON output files.
-   *
-   * @defaultValue false
-   */
-  json?: boolean;
-  /**
-   * If true, the Alloy framework is used to generate Markdown output files.
-   *
-   * @defaultValue false
-   */
-  markdown?: boolean;
-};
-type AlloyPluginUserConfig = BabelPluginUserConfig & {
-  alloy?: AlloyPluginOptions;
-};
-type AlloyPluginResolvedConfig = BabelPluginResolvedConfig & {
-  alloy: AlloyPluginOptions;
-};
-type AlloyPluginContext<TResolvedConfig extends AlloyPluginResolvedConfig = AlloyPluginResolvedConfig> = PluginContext<TResolvedConfig> & {
-  render: (children: Children) => Promise<void>;
-};
-//#endregion
-export { AlloyPluginContext, AlloyPluginOptions, AlloyPluginResolvedConfig, AlloyPluginUserConfig };

package/dist/packages/plugin-automd/src/types/plugin.d.mts

@@ -1,38 +0,0 @@
-import { TOCOptions } from "./toc.mjs";
-import { Config } from "automd";
-
-//#region ../plugin-automd/src/types/plugin.d.ts
-
-type AutoMDPluginOptions = Omit<Config, "dir" | "watch" | "onWatch" | "prefix"> & {
-  /**
-   * Path to the AutoMD configuration file.
-   *
-   * @remarks
-   * If not provided, the plugin will use the default AutoMD configuration resolution mechanism.
-   */
-  configFile?: string;
-  /**
-   * An indicator specifying whether or not issues found by AutoMD during the prepare task are considered fatal.
-   *
-   * @defaultValue true
-   */
-  allowIssues?: boolean;
-  /**
-   * Alternate prefix strings to use for finding generators
-   *
-   * @remarks
-   * By default, AutoMD looks for generators with the "automd" prefix, so that any `<!-- automd:generator [...args] --> ... <!-- /automd -->` comments will be picked up. If you want to use different prefixes (for example, to avoid conflicts with other tools), you would provide a value like "myPrefix" and AutoMD would also look for `<!-- myPrefix:generator [...args] --> ... <!-- /myPrefix -->` comments.
-   *
-   * @defaultValue ["automd", "powerlines", "\{framework\}"]
-   */
-  prefix?: string | string[];
-  /**
-   * Table of Contents generator options
-   *
-   * @remarks
-   * If set to `false`, the built-in Table of Contents generator will be disabled.
-   */
-  toc?: false | TOCOptions;
-};
-//#endregion
-export { AutoMDPluginOptions };

package/dist/packages/plugin-automd/src/types/toc.d.mts

@@ -1,33 +0,0 @@
-//#region ../plugin-automd/src/types/toc.d.ts
-interface TOCOptions {
-  /**
-   * A slugify function to generate slugs for the headings.
-   */
-  slugify?: (str: string) => string;
-  /**
-   * The maximum depth of headings to include in the TOC.
-   *
-   * @defaultValue 6
-   */
-  maxDepth?: number;
-  /**
-   * Whether to include the first H1 heading in the TOC.
-   */
-  firstH1?: boolean;
-  /**
-   * The bullet character to use for list items in the TOC.
-   *
-   * @defaultValue "-"
-   */
-  bullets?: string;
-  /**
-   * A prefix to add to each heading in the TOC.
-   */
-  prefix?: string;
-  /**
-   * A filter function to determine which headings to include in the TOC.
-   */
-  filter?: (str: string, level: number) => boolean;
-}
-//#endregion
-export { TOCOptions };

package/dist/packages/plugin-babel/src/types/plugin.d.mts

@@ -1,15 +0,0 @@
-import { BabelUserConfig, UserConfig } from "../../../powerlines/src/types/config.mjs";
-import { BabelResolvedConfig, ResolvedConfig } from "../../../powerlines/src/types/resolved.mjs";
-import { PluginContext } from "../../../powerlines/src/types/context.mjs";
-
-//#region ../plugin-babel/src/types/plugin.d.ts
-type BabelPluginOptions = Partial<BabelUserConfig>;
-type BabelPluginUserConfig = UserConfig;
-interface BabelPluginResolvedConfig extends ResolvedConfig {
-  transform: {
-    babel: BabelResolvedConfig;
-  };
-}
-type BabelPluginContext<TResolvedConfig extends BabelPluginResolvedConfig = BabelPluginResolvedConfig> = PluginContext<TResolvedConfig>;
-//#endregion
-export { BabelPluginContext, BabelPluginOptions, BabelPluginResolvedConfig, BabelPluginUserConfig };

package/dist/packages/plugin-env/src/types/plugin.d.mts

@@ -1,148 +0,0 @@
-import { Reflection } from "../../../deepkit/src/types.mjs";
-import { BabelPluginContext, BabelPluginOptions, BabelPluginResolvedConfig, BabelPluginUserConfig } from "../../../plugin-babel/src/types/plugin.mjs";
-import { AlloyPluginContext, AlloyPluginOptions, AlloyPluginResolvedConfig, AlloyPluginUserConfig } from "../../../plugin-alloy/src/types/plugin.mjs";
-import { AutoMDPluginOptions } from "../../../plugin-automd/src/types/plugin.mjs";
-import { EnvInterface, SecretsInterface } from "./runtime.mjs";
-import { DotenvConfiguration, TypeDefinition, TypeDefinitionParameter } from "@stryke/types/configuration";
-import { Children } from "@alloy-js/core";
-import { DotenvParseOutput } from "@stryke/env/types";
-
-//#region ../plugin-env/src/types/plugin.d.ts
-type EnvPluginOptions = Omit<DotenvConfiguration, "types"> & {
-  /**
-   * A path to the type definition for the expected env configuration parameters. This value can include both a path to the typescript file and the name of the type definition to use separated by a `":"` or `"#"` character. For example: `"./src/types/env.ts#ConfigConfiguration"`.
-   */
-  types?: TypeDefinitionParameter;
-  /**
-   * A path to the type definition for the expected env secret parameters. This value can include both a path to the typescript file and the name of the type definition to use separated by a `":"` or `"#"` character. For example: `"./src/types/env.ts#ConfigSecrets"`.
-   */
-  secrets?: TypeDefinitionParameter;
-  /**
-   * An additional prefix (or list of additional prefixes) to apply to the environment variables
-   *
-   * @remarks
-   * By default, the plugin will use the `POWERLINES_` prefix. This option is useful for avoiding conflicts with other environment variables.
-   */
-  prefix?: string | string[];
-  /**
-   * Should the plugin inject the env variables in the source code with their values?
-   *
-   * @defaultValue false
-   */
-  inject?: boolean;
-  /**
-   * The default configuration to use when loading environment variables.
-   *
-   * @remarks
-   * This configuration is used as the base configuration when loading environment variables, and will be overridden by any values found in the `.env` file or the process environment.
-   */
-  defaultConfig?: Children;
-  /**
-   * Babel configuration options to use when injecting environment variables into the source code.
-   *
-   * @remarks
-   * This option allows you to customize the Babel transformation process used to inject environment variables into the source code. If not provided, the plugin will use default Babel settings.
-   */
-  babel?: BabelPluginOptions;
-  /**
-   * AutoMD configuration options to allow injecting environment variables documentation into a markdown file such as a README.md.
-   *
-   * @remarks
-   * The README.md file should contain the `<!-- automd:env --><!-- /automd -->` comment block where the documentation will be injected.
-   */
-  automd?: AutoMDPluginOptions;
-  /**
-   * Alloy configuration options to use when injecting environment variables into the source code.
-   *
-   * @remarks
-   * This option allows you to customize the Alloy transformation process used to inject environment variables into the source code. If not provided, the plugin will use default Alloy settings.
-   */
-  alloy?: AlloyPluginOptions;
-};
-type EnvPluginUserConfig = BabelPluginUserConfig & AlloyPluginUserConfig & {
-  env: EnvPluginOptions;
-};
-type EnvPluginResolvedConfig = BabelPluginResolvedConfig & AlloyPluginResolvedConfig & {
-  env: Required<Pick<DotenvConfiguration, "additionalFiles">> & Required<Pick<EnvPluginOptions, "defaultConfig">> & {
-    /**
-     * The type definition for the expected env variable parameters
-     *
-     * @remarks
-     * This value is parsed from the {@link EnvPluginOptions.types} option.
-     */
-    types: TypeDefinition;
-    /**
-     * The type definition for the expected env secret parameters
-     *
-     * @remarks
-     * This value is parsed from the {@link EnvPluginOptions.secrets} option.
-     */
-    secrets: TypeDefinition;
-    /**
-     * Should the plugin inject the env variables in the source code with their values?
-     *
-     * @remarks
-     * This value is the result of reflecting the {@link EnvPluginOptions.inject} option.
-     */
-    inject: EnvPluginOptions["inject"];
-    /**
-     * The prefix used for environment variables
-     *
-     * @remarks
-     * This value is used to filter environment variables that are loaded from the .env file and the process environment.
-     */
-    prefix: string[];
-  };
-};
-interface EnvPluginContext<TResolvedConfig extends EnvPluginResolvedConfig = EnvPluginResolvedConfig> extends BabelPluginContext<TResolvedConfig>, AlloyPluginContext<TResolvedConfig> {
-  env: {
-    /**
-     * The type definitions reflection for the env variables and secrets
-     *
-     * @remarks
-     * These reflections contains the structure of the expected environment variables and secrets as defined by the type definitions provided in the plugin configuration.
-     */
-    types: {
-      /**
-       * The type definitions for the expected env variables
-       */
-      env: Reflection;
-      /**
-       * The type definitions for the expected env secrets
-       */
-      secrets: Reflection;
-    };
-    /**
-     * The current **used** environment variables and secrets reflection
-     *
-     * @remarks
-     * This reflection contains the structure of the current environment variables and secrets as defined during the plugin initialization by extracting the values from the source code.
-     */
-    used: {
-      /**
-       * The current env variables reflection
-       */
-      env: Reflection<EnvInterface>;
-      /**
-       * The current env secrets reflection
-       */
-      secrets: Reflection<SecretsInterface>;
-    };
-    /**
-     * The parsed .env configuration object
-     *
-     * @remarks
-     * This value is the result of loading the .env configuration file found in the project root directory and merging it with the values provided at {@link EnvPluginOptions.values}
-     */
-    parsed: DotenvParseOutput;
-    /**
-     * The injected environment variables and secrets reflection
-     *
-     * @remarks
-     * This reflection contains the structure of the injected environment variables and secrets that were injected into the source code during the build process.
-     */
-    injected: Reflection;
-  };
-}
-//#endregion
-export { EnvPluginContext, EnvPluginOptions, EnvPluginResolvedConfig, EnvPluginUserConfig };