ph-cmd 6.0.0-dev.6 → 6.0.0-dev.7

package/dist/src/help.d.ts

@@ -1,25 +0,0 @@
-/**
- * Help text for CLI commands
- * This file centralizes all help text to keep command files clean
- */
-/**
- * Help text for the update command
- */
-export declare const updateHelp = "\nCommand Overview:\n  The update command helps you manage and update Powerhouse dependencies in your project. It provides\n  an efficient way to keep your project up-to-date with the latest versions of Powerhouse packages.\n  \n  This command:\n  1. Updates all Powerhouse dependencies based on the semver ranges specified in your package.json\n  2. Can force update all dependencies to a specific environment version (dev, prod, latest)\n  3. Automatically builds any local dependencies before updating\n  4. Works with all dependencies with @powerhousedao/ prefix and special packages like document-model\n\nOptions:\n  --force <env>         Force update to the latest available version for the environment specified.\n                        Valid environments: dev, prod, latest.\n                        - dev: Uses @dev tag for all dependencies\n                        - prod/latest: Uses @latest tag for all dependencies\n                        \n  --package-manager     Override the auto-detected package manager with the specified one.\n                        \n  --debug               Show additional logs while executing the command.\n\nSpecial Cases:\n  - Local Dependencies: If you have dependencies linked from a local monorepo (using file: or link:\n    protocols), the command will detect the monorepo root, build affected packages, then update.\n  \n  - No Dependencies: If no Powerhouse dependencies are found in your project, the command will\n    display a message and exit without making changes.\n\nExamples:\n  $ ph update                          # Update dependencies based on package.json ranges\n  $ ph update --force dev              # Force update to latest dev version available\n  $ ph update --force prod             # Force update to latest stable version available (same as latest)\n  $ ph update --force latest           # Force update to latest stable version available (same as prod)\n  $ ph update --package-manager pnpm   # Specify package manager to use\n  $ ph update --debug                  # Show debug information during update\n";
-/**
- * Help text for the use command
- */
-export declare const useHelp = "\nCommand Overview:\n  The use command allows you to quickly switch between different environments for all Powerhouse\n  dependencies in your project. It provides a convenient way to toggle between development,\n  production, local versions, or a specific version of the packages.\n\n  This command:\n  1. Updates all installed Powerhouse dependencies to the specified environment or version\n  2. Can link to local dependencies from a monorepo for development\n  3. Only updates dependencies that are already present in your package.json\n  4. Supports special packages without the @powerhousedao prefix\n\nArguments:\n  <environment>         Required. The environment or version to use. Valid options:\n                        - dev: Use development versions (@dev tag)\n                        - staging: Use staging versions (@staging tag)\n                        - prod/latest: Use production versions (@latest tag)\n                        - local: Use local filesystem versions (requires localPath)\n                        - <version>: Use a specific version (e.g., 5.1.0, 1.0.0-beta.1)\n\n  [localPath]           Path to the local monorepo. Required when environment is 'local'.\n                        This should be the root of your Powerhouse monorepo.\n\nOptions:\n  --force               Force environment to use, even if not in the predefined list\n\n  --package-manager     Override the auto-detected package manager with the specified one.\n\n  --debug               Show additional logs during execution for troubleshooting.\n\n  --use-resolved        Resolves tags to their actual version numbers. For example:\n                        - @dev tag will be resolved to the latest dev version (e.g. v1.0.1-dev.1)\n                        - @latest tag will be resolved to the latest stable version (e.g. v1.0.0)\n                        This ensures you get the exact version that matches the tag.\n\nSpecial Cases:\n  - Local Development: When using the 'local' environment, dependencies are linked directly\n    to local filesystem paths, allowing for real-time development and testing.\n\n  - Missing Dependencies: The command only updates Powerhouse dependencies that are already\n    installed in your project. It won't add new ones.\n\nExamples:\n  $ ph use dev                       # Switch all dependencies to development versions\n  $ ph use staging                   # Switch all dependencies to staging versions\n  $ ph use prod                      # Switch all dependencies to production versions\n  $ ph use latest                    # Same as 'prod', use latest production versions\n  $ ph use 5.1.0                     # Switch all dependencies to version 5.1.0\n  $ ph use 1.0.0-beta.1              # Switch all dependencies to a pre-release version\n  $ ph use local /path/to/monorepo   # Link to local versions in the specified monorepo\n  $ ph use dev --package-manager npm # Use npm instead of the auto-detected package manager\n  $ ph use dev --debug               # Show debug information during execution\n  $ ph use dev --use-resolved        # Resolve @dev tags to actual version numbers (e.g. v1.0.1-dev.1)\n";
-/**
- * Help text for the setup-globals command
- */
-export declare const setupGlobalsHelp = "\nCommand Overview:\n  The setup-globals command initializes a new Powerhouse project with the necessary global \n  configuration. It helps you set up a project quickly with proper defaults and dependencies.\n\n  This command:\n  1. Creates a new project with the specified name or in the current directory\n  2. Sets up all required Powerhouse dependencies\n  3. Configures the project with appropriate settings\n  4. Can run in interactive mode to guide you through the setup process\n\nArguments:\n  [project-name]        Optional. Name of the project to create. If not provided,\n                        the command will use the current directory.\n\nOptions:\n  -p, --project         Specify the name of the project to create.\n                        \n  -i, --interactive     Run the command in interactive mode, which will guide you\n                        through the setup process with questions and prompts.\n                        \n  -v, --version         Specify the development version to use. Defaults to \"main\".\n                        \n  --dev                 Use the \"development\" version of the boilerplate.\n                        \n  --staging             Use the \"staging\" version of the boilerplate.\n                        \n  --package-manager     Override the auto-detected package manager with the specified one.\n\nProject Structure:\n  The command will set up a project with the following structure:\n  - Proper configuration files for TypeScript and ESLint\n  - Dependencies for Powerhouse packages\n  - Build and development scripts\n\nExamples:\n  $ ph setup-globals my-project          # Create a new project named \"my-project\"\n  $ ph setup-globals                     # Set up a project in the current directory\n  $ ph setup-globals -i                  # Run setup in interactive mode\n  $ ph setup-globals --dev               # Use development version\n  $ ph setup-globals -v beta             # Use specific version\n  $ ph setup-globals --package-manager npm   # Use npm as package manager\n";
-/**
- * Help text for the init command
- */
-export declare const initHelp = "\nCommand Overview:\n  The init command creates a new Powerhouse project with optimal defaults. It sets up a fully \n  configured project structure with all necessary dependencies, configurations, and boilerplate.\n\n  This command:\n  1. Creates a new project with the specified name\n  2. Installs all required dependencies for Powerhouse development\n  3. Sets up a proper project structure and configuration files\n  4. Can run in interactive mode for customized setup\n\nArguments:\n  [project-name]        Optional. Name of the project to create. If not provided,\n                        you'll be prompted to provide a name, or the current directory \n                        will be used if in interactive mode.\n\nOptions:\n  -p, --project         Specify the name of the project to create.\n                        \n  -i, --interactive     Run the command in interactive mode, which will guide you\n                        through the project setup with customizable options.\n  \n  -t, --tag             Version of the Powerhouse dependencies to use. Defaults to \"main\"\n                        \n  --dev                 Use the \"development\" version.\n                        \n  --staging             Use the \"staging\" version.\n\n  -b, --branch          Specify custom boilerplate branch to use.\n                        \n  --package-manager     Override the auto-detected package manager with the specified one.\n\nProject Structure:\n  The command will create a complete project with:\n  - Properly configured TypeScript and build settings\n  - Powerhouse document-model integration\n  - All necessary package.json dependencies\n  - Development scripts and tooling\n\nExamples:\n  $ ph init my-awesome-project                                # Create a new project named \"my-awesome-project\"\n  $ ph init -i                                                # Create a project in interactive mode\n  $ ph init -p my-project                                     # Same as ph init my-project\n  $ ph init --dev                                             # Use development version of boilerplate\n  $ ph init -v beta                                           # Use specific version\n  $ ph init --package-manager yarn                            # Use yarn as package manager\n  $ ph init my-awesome-project --dev --package-manager pnpm   # Create a project with Powerhouse dev packages and pnpm as package manager\n";
-/**
- * Help text for the checkout command
- */
-export declare const checkoutHelp = "\nCommand Overview:\n  The checkout command clones an existing Powerhouse project from a remote Vetra drive.\n  This allows you to work on projects that have been initialized and configured by others.\n\n  This command:\n  1. Fetches the GitHub repository URL from the specified Vetra remote drive\n  2. Clones the repository to your local machine\n  3. Installs all project dependencies\n\nRequired Options:\n  -r, --remote-drive <url>   URL of the Vetra remote drive containing the project.\n                             The drive must have a Vetra package with a configured GitHub URL.\n\nOptions:\n  --package-manager <pm>     Specify which package manager to use for installing dependencies.\n                             Supported: npm, yarn, pnpm, bun\n                             If not specified, uses the detected package manager from your environment.\n\nExamples:\n  $ ph checkout --remote-drive https://vetra.example.com/d/abc123                  # Clone project using default package manager\n  $ ph checkout --remote-drive https://vetra.example.com/d/abc123 --package-manager pnpm   # Clone and install with pnpm\n\nNotes:\n  - The remote drive must contain a Vetra package document with a GitHub URL configured\n  - If no GitHub URL is found, you'll need to use 'ph init --remote-drive' instead to create a new project\n  - The repository will be cloned into a directory named after the repository\n";
-//# sourceMappingURL=help.d.ts.map

package/dist/src/help.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"help.d.ts","sourceRoot":"","sources":["../../src/help.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH;;GAEG;AACH,eAAO,MAAM,UAAU,miEAmCtB,CAAC;AAEF;;GAEG;AACH,eAAO,MAAM,OAAO,slGAqDnB,CAAC;AAEF;;GAEG;AACH,eAAO,MAAM,gBAAgB,kgEA0C5B,CAAC;AAEF;;GAEG;AACH,eAAO,MAAM,QAAQ,w4EA+CpB,CAAC;AAEF;;GAEG;AACH,eAAO,MAAM,YAAY,64CA2BxB,CAAC"}

package/dist/src/help.js

@@ -1,230 +0,0 @@
-/**
- * Help text for CLI commands
- * This file centralizes all help text to keep command files clean
- */
-/**
- * Help text for the update command
- */
-export const updateHelp = `
-Command Overview:
-  The update command helps you manage and update Powerhouse dependencies in your project. It provides
-  an efficient way to keep your project up-to-date with the latest versions of Powerhouse packages.
-  
-  This command:
-  1. Updates all Powerhouse dependencies based on the semver ranges specified in your package.json
-  2. Can force update all dependencies to a specific environment version (dev, prod, latest)
-  3. Automatically builds any local dependencies before updating
-  4. Works with all dependencies with @powerhousedao/ prefix and special packages like document-model
-
-Options:
-  --force <env>         Force update to the latest available version for the environment specified.
-                        Valid environments: dev, prod, latest.
-                        - dev: Uses @dev tag for all dependencies
-                        - prod/latest: Uses @latest tag for all dependencies
-                        
-  --package-manager     Override the auto-detected package manager with the specified one.
-                        
-  --debug               Show additional logs while executing the command.
-
-Special Cases:
-  - Local Dependencies: If you have dependencies linked from a local monorepo (using file: or link:
-    protocols), the command will detect the monorepo root, build affected packages, then update.
-  
-  - No Dependencies: If no Powerhouse dependencies are found in your project, the command will
-    display a message and exit without making changes.
-
-Examples:
-  $ ph update                          # Update dependencies based on package.json ranges
-  $ ph update --force dev              # Force update to latest dev version available
-  $ ph update --force prod             # Force update to latest stable version available (same as latest)
-  $ ph update --force latest           # Force update to latest stable version available (same as prod)
-  $ ph update --package-manager pnpm   # Specify package manager to use
-  $ ph update --debug                  # Show debug information during update
-`;
-/**
- * Help text for the use command
- */
-export const useHelp = `
-Command Overview:
-  The use command allows you to quickly switch between different environments for all Powerhouse
-  dependencies in your project. It provides a convenient way to toggle between development,
-  production, local versions, or a specific version of the packages.
-
-  This command:
-  1. Updates all installed Powerhouse dependencies to the specified environment or version
-  2. Can link to local dependencies from a monorepo for development
-  3. Only updates dependencies that are already present in your package.json
-  4. Supports special packages without the @powerhousedao prefix
-
-Arguments:
-  <environment>         Required. The environment or version to use. Valid options:
-                        - dev: Use development versions (@dev tag)
-                        - staging: Use staging versions (@staging tag)
-                        - prod/latest: Use production versions (@latest tag)
-                        - local: Use local filesystem versions (requires localPath)
-                        - <version>: Use a specific version (e.g., 5.1.0, 1.0.0-beta.1)
-
-  [localPath]           Path to the local monorepo. Required when environment is 'local'.
-                        This should be the root of your Powerhouse monorepo.
-
-Options:
-  --force               Force environment to use, even if not in the predefined list
-
-  --package-manager     Override the auto-detected package manager with the specified one.
-
-  --debug               Show additional logs during execution for troubleshooting.
-
-  --use-resolved        Resolves tags to their actual version numbers. For example:
-                        - @dev tag will be resolved to the latest dev version (e.g. v1.0.1-dev.1)
-                        - @latest tag will be resolved to the latest stable version (e.g. v1.0.0)
-                        This ensures you get the exact version that matches the tag.
-
-Special Cases:
-  - Local Development: When using the 'local' environment, dependencies are linked directly
-    to local filesystem paths, allowing for real-time development and testing.
-
-  - Missing Dependencies: The command only updates Powerhouse dependencies that are already
-    installed in your project. It won't add new ones.
-
-Examples:
-  $ ph use dev                       # Switch all dependencies to development versions
-  $ ph use staging                   # Switch all dependencies to staging versions
-  $ ph use prod                      # Switch all dependencies to production versions
-  $ ph use latest                    # Same as 'prod', use latest production versions
-  $ ph use 5.1.0                     # Switch all dependencies to version 5.1.0
-  $ ph use 1.0.0-beta.1              # Switch all dependencies to a pre-release version
-  $ ph use local /path/to/monorepo   # Link to local versions in the specified monorepo
-  $ ph use dev --package-manager npm # Use npm instead of the auto-detected package manager
-  $ ph use dev --debug               # Show debug information during execution
-  $ ph use dev --use-resolved        # Resolve @dev tags to actual version numbers (e.g. v1.0.1-dev.1)
-`;
-/**
- * Help text for the setup-globals command
- */
-export const setupGlobalsHelp = `
-Command Overview:
-  The setup-globals command initializes a new Powerhouse project with the necessary global 
-  configuration. It helps you set up a project quickly with proper defaults and dependencies.
-
-  This command:
-  1. Creates a new project with the specified name or in the current directory
-  2. Sets up all required Powerhouse dependencies
-  3. Configures the project with appropriate settings
-  4. Can run in interactive mode to guide you through the setup process
-
-Arguments:
-  [project-name]        Optional. Name of the project to create. If not provided,
-                        the command will use the current directory.
-
-Options:
-  -p, --project         Specify the name of the project to create.
-                        
-  -i, --interactive     Run the command in interactive mode, which will guide you
-                        through the setup process with questions and prompts.
-                        
-  -v, --version         Specify the development version to use. Defaults to "main".
-                        
-  --dev                 Use the "development" version of the boilerplate.
-                        
-  --staging             Use the "staging" version of the boilerplate.
-                        
-  --package-manager     Override the auto-detected package manager with the specified one.
-
-Project Structure:
-  The command will set up a project with the following structure:
-  - Proper configuration files for TypeScript and ESLint
-  - Dependencies for Powerhouse packages
-  - Build and development scripts
-
-Examples:
-  $ ph setup-globals my-project          # Create a new project named "my-project"
-  $ ph setup-globals                     # Set up a project in the current directory
-  $ ph setup-globals -i                  # Run setup in interactive mode
-  $ ph setup-globals --dev               # Use development version
-  $ ph setup-globals -v beta             # Use specific version
-  $ ph setup-globals --package-manager npm   # Use npm as package manager
-`;
-/**
- * Help text for the init command
- */
-export const initHelp = `
-Command Overview:
-  The init command creates a new Powerhouse project with optimal defaults. It sets up a fully 
-  configured project structure with all necessary dependencies, configurations, and boilerplate.
-
-  This command:
-  1. Creates a new project with the specified name
-  2. Installs all required dependencies for Powerhouse development
-  3. Sets up a proper project structure and configuration files
-  4. Can run in interactive mode for customized setup
-
-Arguments:
-  [project-name]        Optional. Name of the project to create. If not provided,
-                        you'll be prompted to provide a name, or the current directory 
-                        will be used if in interactive mode.
-
-Options:
-  -p, --project         Specify the name of the project to create.
-                        
-  -i, --interactive     Run the command in interactive mode, which will guide you
-                        through the project setup with customizable options.
-  
-  -t, --tag             Version of the Powerhouse dependencies to use. Defaults to "main"
-                        
-  --dev                 Use the "development" version.
-                        
-  --staging             Use the "staging" version.
-
-  -b, --branch          Specify custom boilerplate branch to use.
-                        
-  --package-manager     Override the auto-detected package manager with the specified one.
-
-Project Structure:
-  The command will create a complete project with:
-  - Properly configured TypeScript and build settings
-  - Powerhouse document-model integration
-  - All necessary package.json dependencies
-  - Development scripts and tooling
-
-Examples:
-  $ ph init my-awesome-project                                # Create a new project named "my-awesome-project"
-  $ ph init -i                                                # Create a project in interactive mode
-  $ ph init -p my-project                                     # Same as ph init my-project
-  $ ph init --dev                                             # Use development version of boilerplate
-  $ ph init -v beta                                           # Use specific version
-  $ ph init --package-manager yarn                            # Use yarn as package manager
-  $ ph init my-awesome-project --dev --package-manager pnpm   # Create a project with Powerhouse dev packages and pnpm as package manager
-`;
-/**
- * Help text for the checkout command
- */
-export const checkoutHelp = `
-Command Overview:
-  The checkout command clones an existing Powerhouse project from a remote Vetra drive.
-  This allows you to work on projects that have been initialized and configured by others.
-
-  This command:
-  1. Fetches the GitHub repository URL from the specified Vetra remote drive
-  2. Clones the repository to your local machine
-  3. Installs all project dependencies
-
-Required Options:
-  -r, --remote-drive <url>   URL of the Vetra remote drive containing the project.
-                             The drive must have a Vetra package with a configured GitHub URL.
-
-Options:
-  --package-manager <pm>     Specify which package manager to use for installing dependencies.
-                             Supported: npm, yarn, pnpm, bun
-                             If not specified, uses the detected package manager from your environment.
-
-Examples:
-  $ ph checkout --remote-drive https://vetra.example.com/d/abc123                  # Clone project using default package manager
-  $ ph checkout --remote-drive https://vetra.example.com/d/abc123 --package-manager pnpm   # Clone and install with pnpm
-
-Notes:
-  - The remote drive must contain a Vetra package document with a GitHub URL configured
-  - If no GitHub URL is found, you'll need to use 'ph init --remote-drive' instead to create a new project
-  - The repository will be cloned into a directory named after the repository
-`;
-// Add other command help texts here as needed
-//# sourceMappingURL=help.js.map

package/dist/src/help.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"help.js","sourceRoot":"","sources":["../../src/help.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH;;GAEG;AACH,MAAM,CAAC,MAAM,UAAU,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAmCzB,CAAC;AAEF;;GAEG;AACH,MAAM,CAAC,MAAM,OAAO,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqDtB,CAAC;AAEF;;GAEG;AACH,MAAM,CAAC,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0C/B,CAAC;AAEF;;GAEG;AACH,MAAM,CAAC,MAAM,QAAQ,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA+CvB,CAAC;AAEF;;GAEG;AACH,MAAM,CAAC,MAAM,YAAY,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;CA2B3B,CAAC;AAEF,8CAA8C"}

package/dist/src/index.d.ts

@@ -1,3 +0,0 @@
-export * from "./commands/index.js";
-export * from "./utils/index.js";
-//# sourceMappingURL=index.d.ts.map

package/dist/src/index.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA,cAAc,qBAAqB,CAAC;AACpC,cAAc,kBAAkB,CAAC"}

package/dist/src/index.js

@@ -1,3 +0,0 @@
-export * from "./commands/index.js";
-export * from "./utils/index.js";
-//# sourceMappingURL=index.js.map

package/dist/src/index.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA,cAAc,qBAAqB,CAAC;AACpC,cAAc,kBAAkB,CAAC"}

package/dist/src/types.d.ts

@@ -1,2 +0,0 @@
-export type CommandActionType<Args extends any[], Return = void> = (...args: Args) => Return | Promise<Return>;
-//# sourceMappingURL=types.d.ts.map

package/dist/src/types.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"types.d.ts","sourceRoot":"","sources":["../../src/types.ts"],"names":[],"mappings":"AAAA,MAAM,MAAM,iBAAiB,CAAC,IAAI,SAAS,GAAG,EAAE,EAAE,MAAM,GAAG,IAAI,IAAI,CACjE,GAAG,IAAI,EAAE,IAAI,KACV,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC,CAAC"}

package/dist/src/types.js

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=types.js.map

package/dist/src/types.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"types.js","sourceRoot":"","sources":["../../src/types.ts"],"names":[],"mappings":""}

package/dist/src/utils/constants.d.ts

@@ -1,59 +0,0 @@
-export declare const PH_BIN_PATH: string;
-export declare const PH_BIN = "ph-cli";
-export declare const PH_CLI_COMMANDS: string[];
-export declare const POWERHOUSE_CONFIG_FILE = "powerhouse.config.json";
-export declare const HOME_DIR: string;
-export declare const PH_GLOBAL_DIR_NAME = ".ph";
-export declare const PH_GLOBAL_PACKAGE_NAME = "ph-global";
-export declare const PH_GLOBAL_PROJECT_NAME = ".ph";
-export declare const POWERHOUSE_GLOBAL_DIR: string;
-export declare const packageManagers: {
-    readonly bun: {
-        readonly installCommand: "bun add {{dependency}}";
-        readonly execCommand: "bun ph-cli {{arguments}}";
-        readonly execScript: "bun {{arguments}}";
-        readonly lockfile: "bun.lock";
-        readonly globalPathRegexp: RegExp;
-        readonly updateCommand: "bun update {{dependency}}";
-        readonly buildAffected: "bun run build:affected";
-        readonly workspaceOption: "";
-        readonly installDepsCommand: "bun install";
-    };
-    readonly pnpm: {
-        readonly installCommand: "pnpm add {{dependency}}";
-        readonly execCommand: "pnpm exec ph-cli {{arguments}}";
-        readonly execScript: "pnpm {{arguments}}";
-        readonly lockfile: "pnpm-lock.yaml";
-        readonly globalPathRegexp: RegExp;
-        readonly updateCommand: "pnpm update {{dependency}}";
-        readonly buildAffected: "pnpm run build:affected";
-        readonly workspaceOption: "--workspace-root";
-        readonly installDepsCommand: "pnpm install";
-    };
-    readonly yarn: {
-        readonly installCommand: "yarn add {{dependency}}";
-        readonly execCommand: "yarn ph-cli {{arguments}}";
-        readonly execScript: "yarn {{arguments}}";
-        readonly lockfile: "yarn.lock";
-        readonly globalPathRegexp: RegExp;
-        readonly updateCommand: "yarn upgrade {{dependency}}";
-        readonly buildAffected: "yarn run build:affected";
-        readonly workspaceOption: "-W";
-        readonly installDepsCommand: "yarn install";
-    };
-    readonly npm: {
-        readonly installCommand: "npm install {{dependency}}";
-        readonly execCommand: "npx ph-cli {{arguments}}";
-        readonly execScript: "npm run {{arguments}}";
-        readonly lockfile: "package-lock.json";
-        readonly updateCommand: "npm update {{dependency}} --save";
-        readonly buildAffected: "npm run build:affected";
-        readonly workspaceOption: "";
-        readonly installDepsCommand: "npm install";
-    };
-};
-export declare const PACKAGES_DEPENDENCIES: readonly ["@powerhousedao/builder-tools", "@powerhousedao/codegen", "@powerhousedao/common", "@powerhousedao/config", "@powerhousedao/design-system", "document-drive", "document-model", "@powerhousedao/reactor", "@powerhousedao/reactor-api", "@powerhousedao/reactor-browser", "@powerhousedao/reactor-local", "@powerhousedao/reactor-mcp", "@powerhousedao/switchboard-gui", "@powerhousedao/vetra"];
-export declare const CLIS_DEPENDENCIES: string[];
-export declare const APPS_DEPENDENCIES: string[];
-export declare const ALL_POWERHOUSE_DEPENDENCIES: string[];
-//# sourceMappingURL=constants.d.ts.map

package/dist/src/utils/constants.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"constants.d.ts","sourceRoot":"","sources":["../../../src/utils/constants.ts"],"names":[],"mappings":"AAGA,eAAO,MAAM,WAAW,QAAkB,CAAC;AAC3C,eAAO,MAAM,MAAM,WAAW,CAAC;AAC/B,eAAO,MAAM,eAAe,UAkB3B,CAAC;AACF,eAAO,MAAM,sBAAsB,2BAA2B,CAAC;AAC/D,eAAO,MAAM,QAAQ,QAAY,CAAC;AAClC,eAAO,MAAM,kBAAkB,QAAQ,CAAC;AACxC,eAAO,MAAM,sBAAsB,cAAc,CAAC;AAElD,eAAO,MAAM,sBAAsB,QAAqB,CAAC;AACzD,eAAO,MAAM,qBAAqB,QAA0C,CAAC;AAE7E,eAAO,MAAM,eAAe;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA4ClB,CAAC;AAEX,eAAO,MAAM,qBAAqB,6YAexB,CAAC;AAEX,eAAO,MAAM,iBAAiB,UAAsC,CAAC;AACrE,eAAO,MAAM,iBAAiB,UAG7B,CAAC;AAEF,eAAO,MAAM,2BAA2B,UAIvC,CAAC"}

package/dist/src/utils/constants.js

@@ -1,102 +0,0 @@
-import { homedir } from "node:os";
-import path from "node:path";
-export const PH_BIN_PATH = process.argv[1];
-export const PH_BIN = "ph-cli";
-export const PH_CLI_COMMANDS = [
-    "init",
-    "dev",
-    "connect",
-    "generate",
-    "reactor",
-    "switchboard",
-    "help",
-    "install",
-    "add",
-    "i",
-    "remove",
-    "uninstall",
-    "service",
-    "list",
-    "inspect",
-    "version",
-    "login",
-];
-export const POWERHOUSE_CONFIG_FILE = "powerhouse.config.json";
-export const HOME_DIR = homedir();
-export const PH_GLOBAL_DIR_NAME = ".ph";
-export const PH_GLOBAL_PACKAGE_NAME = "ph-global";
-// Keep PH_GLOBAL_PROJECT_NAME for backwards compatibility
-export const PH_GLOBAL_PROJECT_NAME = PH_GLOBAL_DIR_NAME;
-export const POWERHOUSE_GLOBAL_DIR = path.join(HOME_DIR, PH_GLOBAL_DIR_NAME);
-export const packageManagers = {
-    bun: {
-        installCommand: "bun add {{dependency}}",
-        execCommand: `bun ${PH_BIN} {{arguments}}`,
-        execScript: `bun {{arguments}}`,
-        lockfile: "bun.lock",
-        globalPathRegexp: /[\\/].bun[\\/]/,
-        updateCommand: "bun update {{dependency}}",
-        buildAffected: "bun run build:affected",
-        workspaceOption: "",
-        installDepsCommand: "bun install",
-    },
-    pnpm: {
-        installCommand: "pnpm add {{dependency}}",
-        execCommand: `pnpm exec ${PH_BIN} {{arguments}}`,
-        execScript: `pnpm {{arguments}}`,
-        lockfile: "pnpm-lock.yaml",
-        globalPathRegexp: /[\\/]pnpm[\\/]/,
-        updateCommand: "pnpm update {{dependency}}",
-        buildAffected: "pnpm run build:affected",
-        workspaceOption: "--workspace-root",
-        installDepsCommand: "pnpm install",
-    },
-    yarn: {
-        installCommand: "yarn add {{dependency}}",
-        execCommand: `yarn ${PH_BIN} {{arguments}}`,
-        execScript: `yarn {{arguments}}`,
-        lockfile: "yarn.lock",
-        globalPathRegexp: /[\\/]yarn[\\/]/,
-        updateCommand: "yarn upgrade {{dependency}}",
-        buildAffected: "yarn run build:affected",
-        workspaceOption: "-W",
-        installDepsCommand: "yarn install",
-    },
-    npm: {
-        installCommand: "npm install {{dependency}}",
-        execCommand: `npx ${PH_BIN} {{arguments}}`,
-        execScript: `npm run {{arguments}}`,
-        lockfile: "package-lock.json",
-        updateCommand: "npm update {{dependency}} --save",
-        buildAffected: "npm run build:affected",
-        workspaceOption: "",
-        installDepsCommand: "npm install",
-    },
-};
-export const PACKAGES_DEPENDENCIES = [
-    "@powerhousedao/builder-tools",
-    "@powerhousedao/codegen",
-    "@powerhousedao/common",
-    "@powerhousedao/config",
-    "@powerhousedao/design-system",
-    "document-drive",
-    "document-model",
-    "@powerhousedao/reactor",
-    "@powerhousedao/reactor-api",
-    "@powerhousedao/reactor-browser",
-    "@powerhousedao/reactor-local",
-    "@powerhousedao/reactor-mcp",
-    "@powerhousedao/switchboard-gui",
-    "@powerhousedao/vetra",
-];
-export const CLIS_DEPENDENCIES = ["ph-cmd", "@powerhousedao/ph-cli"];
-export const APPS_DEPENDENCIES = [
-    "@powerhousedao/connect",
-    "@powerhousedao/switchboard",
-];
-export const ALL_POWERHOUSE_DEPENDENCIES = [
-    ...PACKAGES_DEPENDENCIES,
-    ...CLIS_DEPENDENCIES,
-    ...APPS_DEPENDENCIES,
-];
-//# sourceMappingURL=constants.js.map

package/dist/src/utils/constants.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"constants.js","sourceRoot":"","sources":["../../../src/utils/constants.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,SAAS,CAAC;AAClC,OAAO,IAAI,MAAM,WAAW,CAAC;AAE7B,MAAM,CAAC,MAAM,WAAW,GAAG,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;AAC3C,MAAM,CAAC,MAAM,MAAM,GAAG,QAAQ,CAAC;AAC/B,MAAM,CAAC,MAAM,eAAe,GAAG;IAC7B,MAAM;IACN,KAAK;IACL,SAAS;IACT,UAAU;IACV,SAAS;IACT,aAAa;IACb,MAAM;IACN,SAAS;IACT,KAAK;IACL,GAAG;IACH,QAAQ;IACR,WAAW;IACX,SAAS;IACT,MAAM;IACN,SAAS;IACT,SAAS;IACT,OAAO;CACR,CAAC;AACF,MAAM,CAAC,MAAM,sBAAsB,GAAG,wBAAwB,CAAC;AAC/D,MAAM,CAAC,MAAM,QAAQ,GAAG,OAAO,EAAE,CAAC;AAClC,MAAM,CAAC,MAAM,kBAAkB,GAAG,KAAK,CAAC;AACxC,MAAM,CAAC,MAAM,sBAAsB,GAAG,WAAW,CAAC;AAClD,0DAA0D;AAC1D,MAAM,CAAC,MAAM,sBAAsB,GAAG,kBAAkB,CAAC;AACzD,MAAM,CAAC,MAAM,qBAAqB,GAAG,IAAI,CAAC,IAAI,CAAC,QAAQ,EAAE,kBAAkB,CAAC,CAAC;AAE7E,MAAM,CAAC,MAAM,eAAe,GAAG;IAC7B,GAAG,EAAE;QACH,cAAc,EAAE,wBAAwB;QACxC,WAAW,EAAE,OAAO,MAAM,gBAAgB;QAC1C,UAAU,EAAE,mBAAmB;QAC/B,QAAQ,EAAE,UAAU;QACpB,gBAAgB,EAAE,gBAAgB;QAClC,aAAa,EAAE,2BAA2B;QAC1C,aAAa,EAAE,wBAAwB;QACvC,eAAe,EAAE,EAAE;QACnB,kBAAkB,EAAE,aAAa;KAClC;IACD,IAAI,EAAE;QACJ,cAAc,EAAE,yBAAyB;QACzC,WAAW,EAAE,aAAa,MAAM,gBAAgB;QAChD,UAAU,EAAE,oBAAoB;QAChC,QAAQ,EAAE,gBAAgB;QAC1B,gBAAgB,EAAE,gBAAgB;QAClC,aAAa,EAAE,4BAA4B;QAC3C,aAAa,EAAE,yBAAyB;QACxC,eAAe,EAAE,kBAAkB;QACnC,kBAAkB,EAAE,cAAc;KACnC;IACD,IAAI,EAAE;QACJ,cAAc,EAAE,yBAAyB;QACzC,WAAW,EAAE,QAAQ,MAAM,gBAAgB;QAC3C,UAAU,EAAE,oBAAoB;QAChC,QAAQ,EAAE,WAAW;QACrB,gBAAgB,EAAE,gBAAgB;QAClC,aAAa,EAAE,6BAA6B;QAC5C,aAAa,EAAE,yBAAyB;QACxC,eAAe,EAAE,IAAI;QACrB,kBAAkB,EAAE,cAAc;KACnC;IACD,GAAG,EAAE;QACH,cAAc,EAAE,4BAA4B;QAC5C,WAAW,EAAE,OAAO,MAAM,gBAAgB;QAC1C,UAAU,EAAE,uBAAuB;QACnC,QAAQ,EAAE,mBAAmB;QAC7B,aAAa,EAAE,kCAAkC;QACjD,aAAa,EAAE,wBAAwB;QACvC,eAAe,EAAE,EAAE;QACnB,kBAAkB,EAAE,aAAa;KAClC;CACO,CAAC;AAEX,MAAM,CAAC,MAAM,qBAAqB,GAAG;IACnC,8BAA8B;IAC9B,wBAAwB;IACxB,uBAAuB;IACvB,uBAAuB;IACvB,8BAA8B;IAC9B,gBAAgB;IAChB,gBAAgB;IAChB,wBAAwB;IACxB,4BAA4B;IAC5B,gCAAgC;IAChC,8BAA8B;IAC9B,4BAA4B;IAC5B,gCAAgC;IAChC,sBAAsB;CACd,CAAC;AAEX,MAAM,CAAC,MAAM,iBAAiB,GAAG,CAAC,QAAQ,EAAE,uBAAuB,CAAC,CAAC;AACrE,MAAM,CAAC,MAAM,iBAAiB,GAAG;IAC/B,wBAAwB;IACxB,4BAA4B;CAC7B,CAAC;AAEF,MAAM,CAAC,MAAM,2BAA2B,GAAG;IACzC,GAAG,qBAAqB;IACxB,GAAG,iBAAiB;IACpB,GAAG,iBAAiB;CACrB,CAAC"}

package/dist/src/utils/dependencies.d.ts

@@ -1,4 +0,0 @@
-import type { PackageManager } from "./types.js";
-export declare function updateDependencyVersionString(packageManager: PackageManager, dependencies: string[], projectPath: string): void;
-export declare function installDependency(packageManager: PackageManager, dependencies: string[], projectPath: string, workspace?: boolean): void;
-//# sourceMappingURL=dependencies.d.ts.map

package/dist/src/utils/dependencies.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"dependencies.d.ts","sourceRoot":"","sources":["../../../src/utils/dependencies.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EAAe,cAAc,EAAE,MAAM,YAAY,CAAC;AAsB9D,wBAAgB,6BAA6B,CAC3C,cAAc,EAAE,cAAc,EAC9B,YAAY,EAAE,MAAM,EAAE,EACtB,WAAW,EAAE,MAAM,QAmCpB;AAED,wBAAgB,iBAAiB,CAC/B,cAAc,EAAE,cAAc,EAC9B,YAAY,EAAE,MAAM,EAAE,EACtB,WAAW,EAAE,MAAM,EACnB,SAAS,CAAC,EAAE,OAAO,QAuBpB"}

package/dist/src/utils/dependencies.js

@@ -1,61 +0,0 @@
-import { existsSync, readFileSync, writeFileSync } from "fs";
-import { execSync } from "node:child_process";
-import path from "path";
-import { packageManagers } from "./constants.js";
-function parseDependencyString(dependency) {
-    // Handle scoped packages (e.g. @org/package@version)
-    const lastAtIndex = dependency.lastIndexOf("@");
-    if (lastAtIndex === 0) {
-        // This is a scoped package without version
-        return { name: dependency, version: "latest" };
-    }
-    const name = dependency.slice(0, lastAtIndex);
-    const version = dependency.slice(lastAtIndex + 1);
-    return {
-        name,
-        version: version || "latest",
-    };
-}
-export function updateDependencyVersionString(packageManager, dependencies, projectPath) {
-    const manager = packageManagers[packageManager];
-    const packageJsonPath = path.join(projectPath, "package.json");
-    const packageJson = JSON.parse(readFileSync(packageJsonPath, "utf8"));
-    // Initialize dependencies and devDependencies if they don't exist
-    packageJson.dependencies = packageJson.dependencies || {};
-    packageJson.devDependencies = packageJson.devDependencies || {};
-    // Process each dependency string
-    for (const dependency of dependencies) {
-        const { name, version } = parseDependencyString(dependency);
-        // Check if the package exists in either dependencies or devDependencies
-        if (name in packageJson.dependencies) {
-            packageJson.dependencies[name] = version;
-        }
-        else if (name in packageJson.devDependencies) {
-            packageJson.devDependencies[name] = version;
-        }
-    }
-    // Write the updated package.json back to the file
-    writeFileSync(packageJsonPath, JSON.stringify(packageJson, null, 2), "utf8");
-    const installDepsCommand = manager.installDepsCommand;
-    const commandOptions = { cwd: projectPath };
-    execSync(installDepsCommand, {
-        stdio: "inherit",
-        ...commandOptions,
-    });
-}
-export function installDependency(packageManager, dependencies, projectPath, workspace) {
-    if (!existsSync(projectPath)) {
-        throw new Error(`Project path not found: ${projectPath}`);
-    }
-    const manager = packageManagers[packageManager];
-    let installCommand = manager.installCommand.replace("{{dependency}}", dependencies.join(" "));
-    if (workspace) {
-        installCommand += ` ${manager.workspaceOption}`;
-    }
-    const commandOptions = { cwd: projectPath };
-    execSync(installCommand, {
-        stdio: "inherit",
-        ...commandOptions,
-    });
-}
-//# sourceMappingURL=dependencies.js.map

package/dist/src/utils/dependencies.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"dependencies.js","sourceRoot":"","sources":["../../../src/utils/dependencies.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,YAAY,EAAE,aAAa,EAAE,MAAM,IAAI,CAAC;AAC7D,OAAO,EAAE,QAAQ,EAAE,MAAM,oBAAoB,CAAC;AAC9C,OAAO,IAAI,MAAM,MAAM,CAAC;AACxB,OAAO,EAAE,eAAe,EAAE,MAAM,gBAAgB,CAAC;AAGjD,SAAS,qBAAqB,CAAC,UAAkB;IAI/C,qDAAqD;IACrD,MAAM,WAAW,GAAG,UAAU,CAAC,WAAW,CAAC,GAAG,CAAC,CAAC;IAChD,IAAI,WAAW,KAAK,CAAC,EAAE,CAAC;QACtB,2CAA2C;QAC3C,OAAO,EAAE,IAAI,EAAE,UAAU,EAAE,OAAO,EAAE,QAAQ,EAAE,CAAC;IACjD,CAAC;IAED,MAAM,IAAI,GAAG,UAAU,CAAC,KAAK,CAAC,CAAC,EAAE,WAAW,CAAC,CAAC;IAC9C,MAAM,OAAO,GAAG,UAAU,CAAC,KAAK,CAAC,WAAW,GAAG,CAAC,CAAC,CAAC;IAElD,OAAO;QACL,IAAI;QACJ,OAAO,EAAE,OAAO,IAAI,QAAQ;KAC7B,CAAC;AACJ,CAAC;AAED,MAAM,UAAU,6BAA6B,CAC3C,cAA8B,EAC9B,YAAsB,EACtB,WAAmB;IAEnB,MAAM,OAAO,GAAG,eAAe,CAAC,cAAc,CAAC,CAAC;IAEhD,MAAM,eAAe,GAAG,IAAI,CAAC,IAAI,CAAC,WAAW,EAAE,cAAc,CAAC,CAAC;IAC/D,MAAM,WAAW,GAAG,IAAI,CAAC,KAAK,CAC5B,YAAY,CAAC,eAAe,EAAE,MAAM,CAAC,CACvB,CAAC;IAEjB,kEAAkE;IAClE,WAAW,CAAC,YAAY,GAAG,WAAW,CAAC,YAAY,IAAI,EAAE,CAAC;IAC1D,WAAW,CAAC,eAAe,GAAG,WAAW,CAAC,eAAe,IAAI,EAAE,CAAC;IAEhE,iCAAiC;IACjC,KAAK,MAAM,UAAU,IAAI,YAAY,EAAE,CAAC;QACtC,MAAM,EAAE,IAAI,EAAE,OAAO,EAAE,GAAG,qBAAqB,CAAC,UAAU,CAAC,CAAC;QAE5D,wEAAwE;QACxE,IAAI,IAAI,IAAI,WAAW,CAAC,YAAY,EAAE,CAAC;YACrC,WAAW,CAAC,YAAY,CAAC,IAAI,CAAC,GAAG,OAAO,CAAC;QAC3C,CAAC;aAAM,IAAI,IAAI,IAAI,WAAW,CAAC,eAAe,EAAE,CAAC;YAC/C,WAAW,CAAC,eAAe,CAAC,IAAI,CAAC,GAAG,OAAO,CAAC;QAC9C,CAAC;IACH,CAAC;IAED,kDAAkD;IAClD,aAAa,CAAC,eAAe,EAAE,IAAI,CAAC,SAAS,CAAC,WAAW,EAAE,IAAI,EAAE,CAAC,CAAC,EAAE,MAAM,CAAC,CAAC;IAE7E,MAAM,kBAAkB,GAAG,OAAO,CAAC,kBAAkB,CAAC;IACtD,MAAM,cAAc,GAAG,EAAE,GAAG,EAAE,WAAW,EAAE,CAAC;IAE5C,QAAQ,CAAC,kBAAkB,EAAE;QAC3B,KAAK,EAAE,SAAS;QAChB,GAAG,cAAc;KAClB,CAAC,CAAC;AACL,CAAC;AAED,MAAM,UAAU,iBAAiB,CAC/B,cAA8B,EAC9B,YAAsB,EACtB,WAAmB,EACnB,SAAmB;IAEnB,IAAI,CAAC,UAAU,CAAC,WAAW,CAAC,EAAE,CAAC;QAC7B,MAAM,IAAI,KAAK,CAAC,2BAA2B,WAAW,EAAE,CAAC,CAAC;IAC5D,CAAC;IAED,MAAM,OAAO,GAAG,eAAe,CAAC,cAAc,CAAC,CAAC;IAEhD,IAAI,cAAc,GAAG,OAAO,CAAC,cAAc,CAAC,OAAO,CACjD,gBAAgB,EAChB,YAAY,CAAC,IAAI,CAAC,GAAG,CAAC,CACvB,CAAC;IAEF,IAAI,SAAS,EAAE,CAAC;QACd,cAAc,IAAI,IAAI,OAAO,CAAC,eAAe,EAAE,CAAC;IAClD,CAAC;IAED,MAAM,cAAc,GAAG,EAAE,GAAG,EAAE,WAAW,EAAE,CAAC;IAE5C,QAAQ,CAAC,cAAc,EAAE;QACvB,KAAK,EAAE,SAAS;QAChB,GAAG,cAAc;KAClB,CAAC,CAAC;AACL,CAAC"}

package/dist/src/utils/file-system.d.ts

@@ -1,2 +0,0 @@
-export declare function dirExists(path: string): Promise<boolean>;
-//# sourceMappingURL=file-system.d.ts.map

package/dist/src/utils/file-system.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"file-system.d.ts","sourceRoot":"","sources":["../../../src/utils/file-system.ts"],"names":[],"mappings":"AAGA,wBAAsB,SAAS,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC,OAAO,CAAC,CAO9D"}

package/dist/src/utils/file-system.js

@@ -1,12 +0,0 @@
-import { constants } from "node:fs";
-import { access } from "node:fs/promises";
-export async function dirExists(path) {
-    try {
-        await access(path, constants.F_OK);
-        return true;
-    }
-    catch {
-        return false;
-    }
-}
-//# sourceMappingURL=file-system.js.map

package/dist/src/utils/file-system.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"file-system.js","sourceRoot":"","sources":["../../../src/utils/file-system.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,SAAS,EAAE,MAAM,SAAS,CAAC;AACpC,OAAO,EAAE,MAAM,EAAE,MAAM,kBAAkB,CAAC;AAE1C,MAAM,CAAC,KAAK,UAAU,SAAS,CAAC,IAAY;IAC1C,IAAI,CAAC;QACH,MAAM,MAAM,CAAC,IAAI,EAAE,SAAS,CAAC,IAAI,CAAC,CAAC;QACnC,OAAO,IAAI,CAAC;IACd,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,KAAK,CAAC;IACf,CAAC;AACH,CAAC"}

package/dist/src/utils/help-formatting.d.ts

@@ -1,35 +0,0 @@
-import type { Command } from "commander";
-export declare const HELP_FORMATTING_CONFIG: {
-    FIXED_COLUMN_WIDTH: number;
-    COMMANDS_TO_PAD: string[];
-    DESCRIPTION_PADDING: string;
-};
-/**
- * Merges CLI help text with the forwarded PH CLI help text
- * @param {string} cliHelp - Commander-generated help text
- * @param {string} forwardedHelp - Help text from the PH CLI
- * @returns {string} Merged help text
- */
-export declare function mergeHelp(cliHelp: string, forwardedHelp: string): string;
-/**
- * Applies padding to command descriptions for better alignment
- * @param {Command} program - Commander program instance
- */
-export declare function applyCommandPadding(program: Command): void;
-/**
- * Restores original command descriptions after generating help
- * @param {Command} program - Commander program instance
- */
-export declare function restoreCommandDescriptions(program: Command): void;
-/**
- * Captures Commander help output as a string
- * @param {Command} program - Commander program instance
- * @returns {string} Help text as a string
- */
-export declare function captureCommanderHelp(program: Command): string;
-/**
- * Generates and displays the merged help output
- * @param {Command} program - Commander program instance
- */
-export declare function generateMergedHelp(program: Command): Promise<void>;
-//# sourceMappingURL=help-formatting.d.ts.map

package/dist/src/utils/help-formatting.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"help-formatting.d.ts","sourceRoot":"","sources":["../../../src/utils/help-formatting.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAQzC,eAAO,MAAM,sBAAsB;;;;CAOlC,CAAC;AAiEF;;;;;GAKG;AACH,wBAAgB,SAAS,CAAC,OAAO,EAAE,MAAM,EAAE,aAAa,EAAE,MAAM,GAAG,MAAM,CA2DxE;AAED;;;GAGG;AACH,wBAAgB,mBAAmB,CAAC,OAAO,EAAE,OAAO,GAAG,IAAI,CAS1D;AAED;;;GAGG;AACH,wBAAgB,0BAA0B,CAAC,OAAO,EAAE,OAAO,GAAG,IAAI,CAOjE;AAED;;;;GAIG;AACH,wBAAgB,oBAAoB,CAAC,OAAO,EAAE,OAAO,GAAG,MAAM,CAe7D;AAeD;;;GAGG;AACH,wBAAsB,kBAAkB,CAAC,OAAO,EAAE,OAAO,GAAG,OAAO,CAAC,IAAI,CAAC,CA+BxE"}