@karmaniverous/get-dotenv 5.2.2 → 5.2.3

package/README.md

@@ -390,7 +390,7 @@ Diagnostics and CI capture:
 - [Cascade and precedence](./guides/cascade.md)
 - [Shell execution behavior and quoting](./guides/shell.md)
 - [Config files and overlays](./guides/config.md)
-- [Plugin-first host and plugins](./guides/plugins.md)
+- [Plugin-first host and plugins](./guides/plugins/index.md)
 
 The guides are also included in the [hosted API docs](https://docs.karmanivero.us/get-dotenv).
 

package/dist/getdotenv.cli.mjs

@@ -3299,36 +3299,6 @@ const cmdPlugin = (options = {}) => definePlugin({
     },
 });
 
-/**
- * Demo plugin (educational).
- *
- * Purpose
- * - Showcase how to build a plugin for the GetDotenv CLI host.
- * - Demonstrate:
- *   - Accessing the resolved dotenv context (ctx).
- *   - Executing child processes with explicit env injection.
- *   - Resolving commands via scripts and honoring per-script shell overrides.
- *   - Thin adapters: business logic stays minimal; use shared helpers.
- *
- * Key host APIs used:
- * - definePlugin: declare a plugin with setup and optional afterResolve.
- * - cli.ns(name): create a namespaced subcommand under the root CLI.
- * - cli.getCtx(): access \{ optionsResolved, dotenv, plugins?, pluginConfigs? \}.
- *
- * Design notes
- * - We use the shared runCommand() helper so behavior matches the built-in
- *   cmd/batch plugins (env sanitization, plain vs shell execution, stdio).
- * - We inject ctx.dotenv into child env explicitly to avoid bleeding prior
- *   secrets from process.env when exclusions are set (e.g., --exclude-private).
- * - We resolve scripts and shell using shared helpers to honor overrides:
- *   resolveCommand(scripts, input) and resolveShell(scripts, input, shell).
- *
- * Usage (examples)
- *   getdotenv demo ctx
- *   getdotenv demo run --print APP_SETTING
- *   getdotenv demo script echo OK
- *   getdotenv --trace demo run --print ENV_SETTING
- */
 const demoPlugin = () => definePlugin({
     id: 'demo',
     setup(cli) {

package/dist/index.cjs

@@ -3308,36 +3308,6 @@ const cmdPlugin = (options = {}) => definePlugin({
     },
 });
 
-/**
- * Demo plugin (educational).
- *
- * Purpose
- * - Showcase how to build a plugin for the GetDotenv CLI host.
- * - Demonstrate:
- *   - Accessing the resolved dotenv context (ctx).
- *   - Executing child processes with explicit env injection.
- *   - Resolving commands via scripts and honoring per-script shell overrides.
- *   - Thin adapters: business logic stays minimal; use shared helpers.
- *
- * Key host APIs used:
- * - definePlugin: declare a plugin with setup and optional afterResolve.
- * - cli.ns(name): create a namespaced subcommand under the root CLI.
- * - cli.getCtx(): access \{ optionsResolved, dotenv, plugins?, pluginConfigs? \}.
- *
- * Design notes
- * - We use the shared runCommand() helper so behavior matches the built-in
- *   cmd/batch plugins (env sanitization, plain vs shell execution, stdio).
- * - We inject ctx.dotenv into child env explicitly to avoid bleeding prior
- *   secrets from process.env when exclusions are set (e.g., --exclude-private).
- * - We resolve scripts and shell using shared helpers to honor overrides:
- *   resolveCommand(scripts, input) and resolveShell(scripts, input, shell).
- *
- * Usage (examples)
- *   getdotenv demo ctx
- *   getdotenv demo run --print APP_SETTING
- *   getdotenv demo script echo OK
- *   getdotenv --trace demo run --print ENV_SETTING
- */
 const demoPlugin = () => definePlugin({
     id: 'demo',
     setup(cli) {

package/dist/index.mjs

@@ -3305,36 +3305,6 @@ const cmdPlugin = (options = {}) => definePlugin({
     },
 });
 
-/**
- * Demo plugin (educational).
- *
- * Purpose
- * - Showcase how to build a plugin for the GetDotenv CLI host.
- * - Demonstrate:
- *   - Accessing the resolved dotenv context (ctx).
- *   - Executing child processes with explicit env injection.
- *   - Resolving commands via scripts and honoring per-script shell overrides.
- *   - Thin adapters: business logic stays minimal; use shared helpers.
- *
- * Key host APIs used:
- * - definePlugin: declare a plugin with setup and optional afterResolve.
- * - cli.ns(name): create a namespaced subcommand under the root CLI.
- * - cli.getCtx(): access \{ optionsResolved, dotenv, plugins?, pluginConfigs? \}.
- *
- * Design notes
- * - We use the shared runCommand() helper so behavior matches the built-in
- *   cmd/batch plugins (env sanitization, plain vs shell execution, stdio).
- * - We inject ctx.dotenv into child env explicitly to avoid bleeding prior
- *   secrets from process.env when exclusions are set (e.g., --exclude-private).
- * - We resolve scripts and shell using shared helpers to honor overrides:
- *   resolveCommand(scripts, input) and resolveShell(scripts, input, shell).
- *
- * Usage (examples)
- *   getdotenv demo ctx
- *   getdotenv demo run --print APP_SETTING
- *   getdotenv demo script echo OK
- *   getdotenv --trace demo run --print ENV_SETTING
- */
 const demoPlugin = () => definePlugin({
     id: 'demo',
     setup(cli) {

package/dist/plugins-demo.cjs

@@ -188,36 +188,6 @@ const resolveShell = (scripts, command, shell) => scripts && typeof scripts[comm
     ? (scripts[command].shell ?? false)
     : (shell ?? false);
 
-/**
- * Demo plugin (educational).
- *
- * Purpose
- * - Showcase how to build a plugin for the GetDotenv CLI host.
- * - Demonstrate:
- *   - Accessing the resolved dotenv context (ctx).
- *   - Executing child processes with explicit env injection.
- *   - Resolving commands via scripts and honoring per-script shell overrides.
- *   - Thin adapters: business logic stays minimal; use shared helpers.
- *
- * Key host APIs used:
- * - definePlugin: declare a plugin with setup and optional afterResolve.
- * - cli.ns(name): create a namespaced subcommand under the root CLI.
- * - cli.getCtx(): access \{ optionsResolved, dotenv, plugins?, pluginConfigs? \}.
- *
- * Design notes
- * - We use the shared runCommand() helper so behavior matches the built-in
- *   cmd/batch plugins (env sanitization, plain vs shell execution, stdio).
- * - We inject ctx.dotenv into child env explicitly to avoid bleeding prior
- *   secrets from process.env when exclusions are set (e.g., --exclude-private).
- * - We resolve scripts and shell using shared helpers to honor overrides:
- *   resolveCommand(scripts, input) and resolveShell(scripts, input, shell).
- *
- * Usage (examples)
- *   getdotenv demo ctx
- *   getdotenv demo run --print APP_SETTING
- *   getdotenv demo script echo OK
- *   getdotenv --trace demo run --print ENV_SETTING
- */
 const demoPlugin = () => definePlugin({
     id: 'demo',
     setup(cli) {

package/dist/plugins-demo.mjs

@@ -186,36 +186,6 @@ const resolveShell = (scripts, command, shell) => scripts && typeof scripts[comm
     ? (scripts[command].shell ?? false)
     : (shell ?? false);
 
-/**
- * Demo plugin (educational).
- *
- * Purpose
- * - Showcase how to build a plugin for the GetDotenv CLI host.
- * - Demonstrate:
- *   - Accessing the resolved dotenv context (ctx).
- *   - Executing child processes with explicit env injection.
- *   - Resolving commands via scripts and honoring per-script shell overrides.
- *   - Thin adapters: business logic stays minimal; use shared helpers.
- *
- * Key host APIs used:
- * - definePlugin: declare a plugin with setup and optional afterResolve.
- * - cli.ns(name): create a namespaced subcommand under the root CLI.
- * - cli.getCtx(): access \{ optionsResolved, dotenv, plugins?, pluginConfigs? \}.
- *
- * Design notes
- * - We use the shared runCommand() helper so behavior matches the built-in
- *   cmd/batch plugins (env sanitization, plain vs shell execution, stdio).
- * - We inject ctx.dotenv into child env explicitly to avoid bleeding prior
- *   secrets from process.env when exclusions are set (e.g., --exclude-private).
- * - We resolve scripts and shell using shared helpers to honor overrides:
- *   resolveCommand(scripts, input) and resolveShell(scripts, input, shell).
- *
- * Usage (examples)
- *   getdotenv demo ctx
- *   getdotenv demo run --print APP_SETTING
- *   getdotenv demo script echo OK
- *   getdotenv --trace demo run --print ENV_SETTING
- */
 const demoPlugin = () => definePlugin({
     id: 'demo',
     setup(cli) {