@arkebcacy/beacon-cli-temp 0.1.1

package/LICENSE

@@ -0,0 +1,19 @@
+Copyright (c) 2025 ARKE SYSTEMS, LLC
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

package/README.md

@@ -0,0 +1,438 @@
+<div align="center">
+  <img src="./doc/Beacon.webp" alt="Logo" />
+  <h1 align="center">Beacon</h1>
+</div>
+
+Beacon is a command-line tool for serializing and deserializing data from a
+stack in the Contentstack headless CMS platform.
+
+## Overview
+
+Beacon enables full-stack synchronization by allowing users to:
+
+- Serialize (export) a stack's entire contents, including entries, assets,
+  content types, global fields, and taxonomies, into the file system.
+
+- Store the serialized data under version control for tracking and
+  CI/CD deployment.
+
+- Deserialize (import) the stored data into a target stack, restoring
+  its state.
+
+- Create and maintain local backups of stack contents.
+
+- Clear a stack by removing all its contents.
+
+Beacon is particularly useful for teams working with multiple Contentstack
+environments, ensuring content model consistency across development, staging,
+and production.
+
+## Installation
+
+Beacon is available as an NPM package under `@arkebcacy/beacon-cli-temp`. It can
+be installed using any package manager that supports NPM packages.
+
+### Install via Yarn:
+
+```sh
+yarn add --dev @arkebcacy/beacon-cli-temp
+```
+
+### Install via NPM:
+
+```sh
+npm install --save-dev @arkebcacy/beacon-cli-temp
+```
+
+## Usage
+
+Beacon provides a CLI executable named `beacon`. To invoke it, use your
+package manager:
+
+```sh
+yarn beacon <command>
+# or
+npx beacon <command>
+```
+
+### Available Commands
+
+#### `clear`
+
+Completely empties a stack by removing all entries, content types, global
+fields, taxonomies, and assets.
+
+#### `pull`
+
+Serializes a stack's content into the file system for version control or backup.
+
+#### `push`
+
+Deserializes the contents from the file system into the stack.
+
+### Common CLI Options
+
+| Option                       | Description                                     | Required? |
+| ---------------------------- | ----------------------------------------------- | --------- |
+| `--api-key <value>`          | API key for the stack.                          | ✅        |
+| `--api-timeout <value>`      | Timeout for API requests in milliseconds.       | ❌        |
+| `--base-url <value>`         | URL for the Contentstack Management API.        | ✅        |
+| `--branch <value>`           | Stack branch to operate on. Defaults to `main`. | ✅        |
+| `--config-file <value>`      | Path to the YAML configuration file.            | ❌        |
+| `--management-token <value>` | Token for authentication with the stack.        | ✅        |
+| `--environment <value>`      | Named configuration environment.                | ❌        |
+| `--verbose`                  | Enables verbose logging.                        | ❌        |
+| `--help`                     | Displays help information.                      | ❌        |
+
+### Additional Options for `pull` and `push`
+
+| Option                         | Description                                                   | Default       |
+| ------------------------------ | ------------------------------------------------------------- | ------------- |
+| `--schema-path <path>`         | Path to store serialized data.                                | `./cs/schema` |
+| `--extension [name:uid]`       | Maps third-party plugin UIDs to stable names for portability. | N/A           |
+| `--json-rte-plugin [name:uid]` | Similar to `--extension` but for JSON RTE plugins.            | N/A           |
+
+### Additional Options for `push`
+
+| Option                                     | Description                 | Default |
+| ------------------------------------------ | --------------------------- | ------- |
+| `--deletion-strategy <delete,ignore,warn>` | Controls deletion behavior. | `warn`  |
+
+## Handling Third-Party Plugins
+
+Some third-party plugins in Contentstack provide custom field types or JSON RTE
+plugins. Since plugin unique IDs (UIDs) are stack-specific, Beacon provides
+`--extension` and `--json-rte-plugin` options to map these UIDs when
+transferring data between stacks.
+
+### Why is this necessary?
+
+When a third-party plugin, such as Bynder, is installed in a stack, Contentstack
+assigns a unique ID to its custom field type and JSON RTE plugin. These UIDs are
+not exposed in the Contentstack UI, and they are different for every stack. If
+serialized data references these UIDs directly, it may break when restored to
+another stack where the UIDs are different. Beacon allows mapping these UIDs to
+stable names so that they can be translated correctly when deserializing data
+into a different stack.
+
+### How to Find UID Values
+
+To obtain the correct UID values for third-party plugins:
+
+1. **Create a Test Content Type:**
+   - In the Contentstack admin UI, create a new content type that includes the
+     third-party plugin.
+
+   - If the plugin provides a JSON RTE plugin, ensure it is explicitly selected
+     as active for the field.
+
+2. **Export the Content Type:**
+   - Use the Contentstack admin UI to export the content type as JSON. The
+     exported JSON will contain minimized data, making it challenging to read.
+
+3. **Locate the UID Values:**
+   - Within the exported JSON, find the block of JSON that corresponds to the
+     custom field. It will look something like this:
+
+     ```json
+     {
+       "data_type": "json",
+       "display_name": "Background Image",
+       "extension_uid": "blt6b7c082b-example",
+       "field_metadata": { "extension": true },
+       "mandatory": false,
+       "multiple": false,
+       "non_localizable": false,
+       "uid": "background_image",
+       "unique": false
+     }
+     ```
+
+   - The `extension_uid` value (`blt6b7c082b-example` in this example) is the
+     UID for the custom field.
+
+4. **Identify the JSON RTE Plugin UID:**
+   - Similarly, locate the JSON RTE plugin's UID within the exported JSON. It
+     will be nested under the JSON RTE field’s configuration:
+
+     ```json
+     {
+       "data_type": "json",
+       "display_name": "Content",
+       "field_metadata": {},
+       "mandatory": false,
+       "multiple": false,
+       "non_localizable": false,
+       "plugins": ["bltd0dac425-example"],
+       "uid": "content",
+       "unique": false
+     },
+     ```
+
+   - The `plugins` array contains the JSON RTE plugin UID (`bltd0dac425-example`
+     in this example).
+
+5. **Use the UID Values in Beacon:**
+   - Map these UIDs to stable names using `--extension` and `--json-rte-plugin`
+     options:
+
+     ```sh
+     yarn beacon pull \
+       --extension bynder:blt6b7c082b-uid-in-source-stack \
+       --json-rte-plugin bynder:bltd0dac425-uid-in-source-stack
+     ```
+
+   - When pushing data to another stack, use the same mapping:
+
+     ```sh
+     yarn beacon push \
+       --extension bynder:blt6b7c082b-uid-in-target-stack \
+       --json-rte-plugin bynder:bltd0dac425-uid-in-target-stack
+     ```
+
+   - Note: the word `bynder` in the above examples is user-defined and
+     arbitrary. It is used to identify the third-party plugin, and it will be
+     serialized in the data instead of the stack-specific UID values. You can
+     use any name that makes sense to you, except the same name must be used
+     consistently across all commands. It is not a conflict to use the same
+     name for both the `--extension` and `--json-rte-plugin` options.
+
+By following these steps, developers can ensure that serialized content remains
+portable between stacks, preventing UID mismatches that could otherwise
+break integrations.
+
+## Configuration
+
+In addition to the command line, Beacon allows specifying options via
+environment variables or an optional YAML configuration file (`beacon.yaml`).
+
+The order of precedence is:
+
+1. Command line
+2. Environment variables
+3. Configuration file
+
+That is, options specified on the command line have the highest precedence,
+followed by environment variables, and finally the configuration file.
+
+### Environment Variables
+
+| Variable                        | Maps To              | Required? | Default |
+| ------------------------------- | -------------------- | --------- | ------- |
+| `Contentstack_Api_Key`          | `--api-key`          | ✅        | N/A     |
+| `Contentstack_Management_API`   | `--base-url`         | ✅        | N/A     |
+| `Contentstack_Branch`           | `--branch`           | ❌        | `main`  |
+| `Contentstack_Management_Token` | `--management-token` | ✅        | N/A     |
+| `Beacon_Extension`              | `--extension`        | ❌        | N/A     |
+| `Beacon_Plugin`                 | `--json-rte-plugin`  | ❌        | N/A     |
+
+### Configuration File (`beacon.yaml`)
+
+The YAML configuration file allows for additional options.
+
+Example:
+
+```yaml
+# yaml-language-server: $schema=node_modules/@arkebcacy/beacon-cli-temp/dist/cfg/Config.schema.yaml
+
+client:
+  api-key: bltcfcf264c-example
+  management-token: cs-example
+  branch: main
+  base-url: https://api.contentstack.io/
+  timeout: 10000
+
+schema:
+  deletion-strategy: warn # delete | ignore | warn
+  schema-path: ./cs/schema
+
+  extension:
+    Bynder: blt6b7c082b-example
+
+  json-rte-plugin:
+    Bynder: bltdd6396f0-example
+
+  # Include or exclude assets using glob patterns.
+  assets:
+    include: ['**']
+    exclude: []
+
+  # Determine whether to serialize taxonomy terms or just the
+  # taxonomy structure.
+  taxonomies:
+    page_type: taxonomy and terms
+    '*': only taxonomy
+
+environments:
+  dev:
+    client: { api-key: bltcfcf264c-dev-example }
+    schema:
+      deletion-strategy: delete
+      extension: { Bynder: blt6b7c082b-dev-example }
+      json-rte-plugin: { Bynder: bltdd6396f0-dev-example }
+
+  production:
+    client: { api-key: bltcfcf264c-prod-example }
+    schema:
+      deletion-strategy: ignore
+      extension: { Bynder: blt6b7c082b-prod-example }
+      json-rte-plugin: { Bynder: bltdd6396f0-prod-example }
+
+verbose: false
+```
+
+### Named Environments
+
+The configuration file may contain an optional `environments` section. This
+section allows defining multiple named environments, each with its own
+configuration. This is useful for managing different environments (e.g.,
+development, staging, production) with different settings.
+
+The `environments` section is a map of environment names to configuration
+values. Each environment can override the base configuration values
+defined in the `client` and `schema` sections.
+
+When a named environment is specified using the `--environment` option,
+the settings for that environment will be merged with the base
+configuration. During this merge, the following rules apply:
+
+- `schema.extension`, `schema.json-rte-plugin`, and `schema.taxonomies`
+  are merged, with values from the named environment being used _in addition_
+  to values from the base configuration.
+
+- `schema.assets.include` and `schema.assets.exclude` are concatenated,
+  with values from the named environment being _added_ to the base
+  configuration.
+
+- All other values will prefer the named environment.
+
+### Management Tokens
+
+Although the configuration file supports including the management token,
+it is **highly recommended** to omit this value from the configuration file
+for security reasons. Instead, use the `--management-token` command line
+option or set the `Contentstack_Management_Token` environment variable.
+
+## Examples
+
+### Pulling Content from a Stack
+
+```sh
+yarn beacon pull \
+  --api-key bltcfcf264c-example \
+  --management-token cs-example \
+  --base-url https://api.contentstack.io
+```
+
+### Pushing Content to a Stack
+
+```sh
+yarn beacon push \
+  --api-key bltcfcf264c-example \
+  --management-token cs-example \
+  --base-url https://api.contentstack.io
+```
+
+### Clearing a Stack
+
+```sh
+yarn beacon clear \
+  --api-key bltcfcf264c-example \
+  --management-token cs-example \
+  --base-url https://api.contentstack.io
+```
+
+### Cookbook: Project Configuration
+
+The recommended configuration for incorporating Beacon into a project is to
+store any stack-specific settings in the project's `.env` file, outside of
+source control. Any shared team settings can then be stored in the `beacon.yaml`
+file, which should be committed to source control. This permits individual
+developers to target their personal stack and also permits CI/CD tooling to
+operate effectively on higher environments.
+
+For example:
+
+```sh
+# .env (ignored by Git)
+Contentstack_Api_Key=bltcfcf264c-example
+Contentstack_Management_API=https://api.contentstack.io/
+Contentstack_Management_Token=cs-example
+Beacon_Extension=Bynder:blt6b7c082b-example
+Beacon_Plugin=Bynder:bltdd6396f0-example
+```
+
+```sh
+# .env.example (committed to Git)
+Contentstack_Api_Key=
+Contentstack_Management_API=https://api.contentstack.io/
+Contentstack_Management_Token=
+Beacon_Extension=
+Beacon_Plugin=
+```
+
+```yaml
+# beacon.yaml
+schema:
+  schema-path: ./cs/schema
+
+  assets:
+    include:
+      - Chrome/**
+      - Errors/404.jpg
+      - Logo/logo-412.webp
+    taxonomies:
+      page_type: 'taxonomy and terms'
+      '*': only taxonomy
+```
+
+```yaml
+# .yarnrc.yml
+injectEnvironmentFiles: [.env?]
+```
+
+Under this configuration, the push, pull, and clear commands become:
+
+```sh
+yarn beacon pull
+yarn beacon push
+yarn beacon clear
+```
+
+For CI/CD environments, the `.env` file will not exist, so environment variables
+should be set by the CI/CD tooling instead.
+
+## Development
+
+This project uses [yarn][1] as a package manager. Use `yarn install` to install
+the dependencies.
+
+To test locally, you will need an `.env` file. Copy the `.env.example` file to
+create your own `.env` file.
+
+Some development scripts are provided:
+
+- `yarn build` - Compile TypeScript code.
+- `yarn clean` - Remove compiled code.
+- `yarn cli` - Invoke the CLI.
+- `yarn lint` - Invoke ESLint.
+- `yarn pretty` - Invoke Prettier.
+- `yarn test` - Invoke unit tests.
+- `yarn workspace @arkebcacy/beacon-cli-temp generate` - Rebuild OpenAPI type
+  definitions.
+
+## Deployment
+
+This repository provides a CLI tool that can be installed into other projects
+as an NPM package.
+
+New releases of this tool are handled by the `publish-package` GitHub Action.
+To invoke this action, create and publish a [new release][2] in GitHub.
+
+## License
+
+Beacon is licensed under the MIT License.
+
+[1]: https://yarnpkg.com/ 'Yarn package manager'
+[2]: https://github.com/Arke-Systems/beacon/releases/new 'Create a new release'
+[3]: https://yarnpkg.com/configuration/yarnrc#injectEnvironmentFiles 'Yarn Inject Environment Files'

package/dist/beacon.d.ts

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+export {};
+//# sourceMappingURL=beacon.d.ts.map

package/dist/beacon.d.ts.map

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

package/dist/beacon.js

@@ -0,0 +1,15 @@
+#!/usr/bin/env node
+import { Command } from 'commander';
+import clear from './ui/command/clear.js';
+import pull from './ui/command/pull.js';
+import push from './ui/command/push.js';
+import version from './ui/version.js';
+const program = new Command();
+program
+    .version(await version())
+    .description('Beacon CLI')
+    .addCommand(clear)
+    .addCommand(pull)
+    .addCommand(push);
+await program.parseAsync();
+//# sourceMappingURL=beacon.js.map

package/dist/beacon.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"beacon.js","sourceRoot":"","sources":["../src/beacon.ts"],"names":[],"mappings":";AAEA,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AACpC,OAAO,KAAK,MAAM,uBAAuB,CAAC;AAC1C,OAAO,IAAI,MAAM,sBAAsB,CAAC;AACxC,OAAO,IAAI,MAAM,sBAAsB,CAAC;AACxC,OAAO,OAAO,MAAM,iBAAiB,CAAC;AAEtC,MAAM,OAAO,GAAG,IAAI,OAAO,EAAE,CAAC;AAE9B,OAAO;KACL,OAAO,CAAC,MAAM,OAAO,EAAE,CAAC;KACxB,WAAW,CAAC,YAAY,CAAC;KACzB,UAAU,CAAC,KAAK,CAAC;KACjB,UAAU,CAAC,IAAI,CAAC;KAChB,UAAU,CAAC,IAAI,CAAC,CAAC;AAEnB,MAAM,OAAO,CAAC,UAAU,EAAE,CAAC","sourcesContent":["#!/usr/bin/env node\n\nimport { Command } from 'commander';\nimport clear from './ui/command/clear.js';\nimport pull from './ui/command/pull.js';\nimport push from './ui/command/push.js';\nimport version from './ui/version.js';\n\nconst program = new Command();\n\nprogram\n\t.version(await version())\n\t.description('Beacon CLI')\n\t.addCommand(clear)\n\t.addCommand(pull)\n\t.addCommand(push);\n\nawait program.parseAsync();\n"]}

package/dist/cfg/CliOptions.d.ts

@@ -0,0 +1,7 @@
+import type { PathLike } from 'node:fs';
+import type { PartialOptions } from '../ui/PartialOptions.js';
+export type CliOptions = PartialOptions & {
+    readonly configFile: PathLike;
+    readonly namedEnvironment?: string | undefined;
+};
+//# sourceMappingURL=CliOptions.d.ts.map

package/dist/cfg/CliOptions.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"CliOptions.d.ts","sourceRoot":"","sources":["../../src/cfg/CliOptions.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,SAAS,CAAC;AACxC,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,yBAAyB,CAAC;AAE9D,MAAM,MAAM,UAAU,GAAG,cAAc,GAAG;IACzC,QAAQ,CAAC,UAAU,EAAE,QAAQ,CAAC;IAC9B,QAAQ,CAAC,gBAAgB,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;CAC/C,CAAC"}

package/dist/cfg/CliOptions.js

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

package/dist/cfg/CliOptions.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"CliOptions.js","sourceRoot":"","sources":["../../src/cfg/CliOptions.ts"],"names":[],"mappings":"","sourcesContent":["import type { PathLike } from 'node:fs';\nimport type { PartialOptions } from '../ui/PartialOptions.js';\n\nexport type CliOptions = PartialOptions & {\n\treadonly configFile: PathLike;\n\treadonly namedEnvironment?: string | undefined;\n};\n"]}

package/dist/cfg/Config.schema.yaml

@@ -0,0 +1,122 @@
+# yaml-language-server: $schema=http://json-schema.org/draft-07/schema
+
+type: object
+additionalProperties: false
+properties:
+  client: &client
+    type: object
+    additionalProperties: false
+    properties:
+      api-key:
+        type: string
+        minLength: 1
+
+      base-url:
+        type: string
+        minLength: 8
+        format: uri
+
+      branch:
+        type: string
+        minLength: 1
+        default: main
+
+      management-token:
+        type: string
+        minLength: 1
+
+      timeout:
+        type: integer
+        minimum: 1
+        default: 10000
+
+  schema: &schema
+    type: object
+    additionalProperties: false
+    properties:
+      deletion-strategy:
+        type: string
+        enum: ['delete', 'ignore', 'warn']
+        default: warn
+
+      extension:
+        type: object
+        minProperties: 1
+        additionalProperties:
+          type: string
+          minLength: 1
+
+      json-rte-plugin:
+        type: object
+        minProperties: 1
+        additionalProperties:
+          type: string
+          minLength: 1
+
+      schema-path:
+        type: string
+        minLength: 1
+
+      assets:
+        type: object
+        additionalProperties: false
+        description: Include or exclude assets using glob patterns.
+        default:
+          include: ['**']
+          exclude: []
+        properties:
+          include:
+            type: array
+            items:
+              type: string
+              minLength: 1
+          exclude:
+            type: array
+            items:
+              type: string
+              minLength: 1
+
+      taxonomies:
+        type: object
+        minProperties: 1
+
+        description: |
+          Determine whether to serialize taxonomy terms or just the
+          taxonomy structure.
+
+        additionalProperties:
+          type: string
+          enum: ['only taxonomy', 'taxonomy and terms']
+        default:
+          '*': 'taxonomy and terms'
+
+  verbose:
+    type: boolean
+    default: false
+
+  environments:
+    type: object
+    minProperties: 1
+
+    description: |
+      An optional list of named environments. Environment names are arbitrary.
+
+      Named environments may be targetted using the `--environment` option.
+
+      If specified, an environment's settings will be merged with the base
+      settings:
+
+        - `schema.extension`, `schema.json-rte-plugin`, and `schema.taxonomies`
+          are merged.
+
+        - `schema.assets.include` and `schema.assets.exclude` are concatenated.
+
+        - All other values will prefer the named environment.
+
+    additionalProperties:
+      type: object
+      minProperties: 1
+      additionalProperties: false
+      properties:
+        client: *client
+        schema: *schema

package/dist/cfg/ConfigMissingError.d.ts

@@ -0,0 +1,4 @@
+export default class ConfigMissingError extends Error {
+    constructor(message: string);
+}
+//# sourceMappingURL=ConfigMissingError.d.ts.map

package/dist/cfg/ConfigMissingError.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"ConfigMissingError.d.ts","sourceRoot":"","sources":["../../src/cfg/ConfigMissingError.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,OAAO,OAAO,kBAAmB,SAAQ,KAAK;gBACjC,OAAO,EAAE,MAAM;CAIlC"}

package/dist/cfg/ConfigMissingError.js

@@ -0,0 +1,7 @@
+export default class ConfigMissingError extends Error {
+    constructor(message) {
+        super(message);
+        this.name = 'ConfigMissingError';
+    }
+}
+//# sourceMappingURL=ConfigMissingError.js.map

package/dist/cfg/ConfigMissingError.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"ConfigMissingError.js","sourceRoot":"","sources":["../../src/cfg/ConfigMissingError.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,OAAO,OAAO,kBAAmB,SAAQ,KAAK;IACpD,YAAmB,OAAe;QACjC,KAAK,CAAC,OAAO,CAAC,CAAC;QACf,IAAI,CAAC,IAAI,GAAG,oBAAoB,CAAC;IAClC,CAAC;CACD","sourcesContent":["export default class ConfigMissingError extends Error {\n\tpublic constructor(message: string) {\n\t\tsuper(message);\n\t\tthis.name = 'ConfigMissingError';\n\t}\n}\n"]}

package/dist/cfg/ConfigurationError.d.ts

@@ -0,0 +1,9 @@
+import type { ErrorObject } from 'ajv';
+import type { PathLike } from 'node:fs';
+import HandledError from '../ui/HandledError.js';
+export default class ConfigurationError extends HandledError {
+    readonly configPath: PathLike;
+    readonly details: ErrorObject[] | null | undefined;
+    constructor(configPath: PathLike, details: ErrorObject[] | null | undefined);
+}
+//# sourceMappingURL=ConfigurationError.d.ts.map

package/dist/cfg/ConfigurationError.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"ConfigurationError.d.ts","sourceRoot":"","sources":["../../src/cfg/ConfigurationError.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,KAAK,CAAC;AAEvC,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,SAAS,CAAC;AAExC,OAAO,YAAY,MAAM,uBAAuB,CAAC;AAGjD,MAAM,CAAC,OAAO,OAAO,kBAAmB,SAAQ,YAAY;aAE1C,UAAU,EAAE,QAAQ;aACpB,OAAO,EAAE,WAAW,EAAE,GAAG,IAAI,GAAG,SAAS;gBADzC,UAAU,EAAE,QAAQ,EACpB,OAAO,EAAE,WAAW,EAAE,GAAG,IAAI,GAAG,SAAS;CAiB1D"}

package/dist/cfg/ConfigurationError.js

@@ -0,0 +1,23 @@
+import { Ajv } from 'ajv';
+import { inspect } from 'node:util';
+import HandledError from '../ui/HandledError.js';
+import createStylus from '../ui/createStylus.js';
+export default class ConfigurationError extends HandledError {
+    configPath;
+    details;
+    constructor(configPath, details) {
+        const ajv = new Ajv();
+        const y = createStylus('yellowBright');
+        const msg1 = y `Configuration file ${String(configPath)} is invalid:\n\t`;
+        const msg2 = ajv.errorsText(details, {
+            dataVar: 'config',
+            separator: '\n\t',
+        });
+        const msg3 = inspect(details, { colors: true, depth: 3 });
+        super(`${msg1}${msg2}\n\n${msg3}`);
+        this.configPath = configPath;
+        this.details = details;
+        this.name = 'ConfigurationError';
+    }
+}
+//# sourceMappingURL=ConfigurationError.js.map