babelfhir-ts 1.0.28 → 1.0.30

package/LICENSE

@@ -1,15 +1,15 @@
-ISC License
-
-Copyright (c) 2025 Maximilian Nussbaumer
-
-Permission to use, copy, modify, and/or distribute this software for any
-purpose with or without fee is hereby granted, provided that the above
-copyright notice and this permission notice appear in all copies.
-
-THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
-WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
-ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
-WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
-ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
-OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+ISC License
+
+Copyright (c) 2025 Maximilian Nussbaumer
+
+Permission to use, copy, modify, and/or distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

package/README.md

@@ -1,210 +1,226 @@
-# BabelFHIR-TS
-
-[![npm version](https://img.shields.io/npm/v/babelfhir-ts.svg)](https://www.npmjs.com/package/babelfhir-ts)
-[![License: ISC](https://img.shields.io/badge/License-ISC-blue.svg)](https://opensource.org/licenses/ISC)
-[![TypeScript](https://img.shields.io/badge/TypeScript-5.8-blue)](https://www.typescriptlang.org/)
-[![Node.js](https://img.shields.io/badge/Node.js-18%2B-green)](https://nodejs.org/)
-
-**BabelFHIR-TS** transforms FHIR® StructureDefinitions into production-ready TypeScript code with full type safety and built-in validation. Unlike generic FHIR type definitions, BabelFHIR-TS generates **profile-aware** interfaces that understand your Implementation Guide's constraints, extensions, and slicing rules.
-
-### What you get
-
-- **Strongly typed interfaces** that merge profile constraints with base FHIR types (types come from `@types/fhir`)
-- **Compiled output by default** — packages ship JavaScript (`.js`) plus TypeScript declarations (`.d.ts`)
-- **Runtime validation** using FHIRPath expressions from the profile—no external validator required for basic checks
-- **Type-safe extension handling** with proper slicing and nested extension support
-- **Random data builders** for testing and development (when class generation is enabled)
-- **Zero manual mapping**—consume any FHIR package or Implementation Guide directly from registries
-- **Fast and lightweight**—minimal runtime deps; only `fhirpath` is required for validators
-- **Install any FHIR profile as a node module**—use `babelfhir-ts install` to add Implementation Guides directly to your project
-
-## Installation
-
-Install globally (recommended when using the CLI frequently):
-
-```bash
-npm install -g babelfhir-ts
-```
-
-Or invoke on-demand without a global install:
-
-```bash
-npx babelfhir-ts --help
-```
-
-> **Requirements:** Node.js 18+ (ESM support) and an internet connection when downloading packages from remote registries.
-
-## Quick start
-
-Generate code from a local folder that contains FHIR packages:
-
-```bash
-babelfhir-ts input/ output/
-```
-
-Process a single package archive and write the generated interfaces back into a new `.tgz` file:
-
-```bash
-babelfhir-ts hl7.fhir.us.core-8.0.0.tgz us-core-generated.tgz
-```
-
-Download and process a package directly from a registry (defaults to `https://packages.simplifier.net`):
-
-```bash
-babelfhir-ts --package hl7.fhir.us.core@8.0.0
-```
-
-Download, pocess and install a processed package into your current project:
-
-```bash
-babelfhir-ts install hl7.fhir.us.core@8.0.0
-```
-
-After generation you can import the emitted classes:
-
-```ts
-import { USCorePatientClass } from "./output/USCorePatientClass";
-
-const patient = USCorePatientClass.random();
-const { errors, warnings } = await patient.validate();
-```
-
-## Using the generated code in your project
-
-Generated profile packages installed via `babelfhir-ts install` are published as **compiled JavaScript with TypeScript declarations**:
-
-- JavaScript for runtime: `index.js`, `*.js`
-- Type declarations for IDE/TS: `index.d.ts`, `*.d.ts`
-- Dependencies:
-  - `@types/fhir` is included as a dependency of the generated package (no extra setup in your app)
-  - `fhirpath` is a peer dependency (required only if you use the generated validators/classes)
-
-Install `fhirpath` in your app if you plan to call `.validate()` or use the generated classes.
-
-### Module resolution
-
-Generated packages work with all modern TypeScript setups:
-
-- **Node.js 18+** with `"type": "module"` in `package.json`
-- **Bundlers** (Vite, esbuild, Webpack) with ESM output
-- **TypeScript 5.0+** with any module resolution (`node16`, `nodenext`, or `bundler`)
-
-#### FHIR type imports
-
-Generated code imports base FHIR types from `"fhir/r4"`:
-
-```ts
-import { Appointment, Extension, CodeableConcept } from "fhir/r4";
-```
-
-Since `@types/fhir` doesn't provide a `package.json` `exports` field, BabelFHIR-TS includes an **ambient module declaration** (`fhir-r4.d.ts`) in every generated package. The generated `index.d.ts` references this file:
-
-```ts
-/// <reference path="./fhir-r4.d.ts" />
-```
-
-This ensures TypeScript can resolve `fhir/r4` imports automatically without any configuration in your project's `tsconfig.json`.
-
-## CLI reference
-
-```
-babelfhir-ts [options] [<input> [output]]
-```
-
-| Argument / option           | Description                                                                                                                                                         |
-| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `<input>`                 | Directory of FHIR packages/StructureDefinitions, single package (`.tgz`/`.zip`), or single StructureDefinition `.json`. Defaults to `./input` when omitted. |
-| `<output>`                | Destination directory or archive. Defaults to `./output` when omitted.                                                                                            |
-| `install`                 | Downloads, processes, and installs a package as a project dependency.                                                                                               |
-| `--package <pkg@version>` | Fetch a package from a registry and process it without manual download.                                                                                             |
-| `--registry <url>`        | Custom registry base URL (default:`https://packages.simplifier.net`).                                                                                             |
-| `--log <level>`           | Control logging output:`none` (default), `console`, or `file`.                                                                                                |
-| `--no-cache`              | Remove the `.cache` directory once generation completes.                                                                                                          |
-| `--no-classes`            | Skip emitting helper classes (interfaces & validators only).                                                                                                        |
-| `-h, --help`              | Print usage help.                                                                                                                                                   |
-| `-v, --version`           | Print the BabelFHIR-TS version.                                                                                                                                     |
-
-### Supported inputs
-
-- **Directory** – scan all `.tgz`, `.zip`, or `.json` files inside the folder
-- **Archive** – process a FHIR NPM package in `.tgz` or `.zip` format
-- **StructureDefinition JSON** – generate code for a single profile definitio
-
-## Scripts for contributors
-
-| Script                         | Purpose                                                                      |
-| ------------------------------ | ---------------------------------------------------------------------------- |
-| `npm run generate`           | Execute the CLI against the local `input/` folder and refresh `output/`. |
-| `npm run generate:check`     | End-to-end check: generate, type-check, and lint the emitted output.         |
-| `npm test`                   | Type-check and run all Vitest suites (coverage enabled).                     |
-| `npm run download-validator` | Fetch the official HL7 validation jar used for parity testing.               |
-
-## Caching notes
-
-The generator caches downloaded StructureDefinitions and packages inside `.cache/`. When you need a clean run, pass `--no-cache` or manually remove the folder. Temporary downloads land in `.temp-*` directories and are cleaned up automatically.
-
-## Why BabelFHIR-TS?
-
-**The FHIR Challenge**: Implementation Guides define strict profiles that constrain base FHIR resources with required or must-support elements, custom extensions, value set bindings, and cardinality rules. Existing TypeScript libraries can't capture these requirements when you need profile-specific types, leading to an overhead when using TypeScript to build apps that interact with FHIR servers.
-
-**The BabelFHIR-TS Solution**: Automatically generates TypeScript interfaces and validation logic directly from StructureDefinition JSON. Your IDE autocompletes required fields, flags missing extensions at compile-time, and validates FHIRPath invariants at runtime.
-
-## Limitations
-
-BabelFHIR-TS is a code generation tool that parses FHIR StructureDefinitions and produces TypeScript interfaces and validators. While it handles many common FHIR profiling patterns, there are important limitations to be aware of:
-
-### Profile Mapping Accuracy
-
-- **Not guaranteed for all IGs**: The generator uses heuristics to interpret StructureDefinition constraints, slicing rules, and extensions. Complex or unusual profiling patterns may not map correctly to TypeScript.
-- **Test before production**: Always validate the generated code against your specific Implementation Guide's examples and test cases. We recommend running the official FHIR validator alongside BabelFHIR-TS in your QA pipeline.
-- **Edge cases**: Rare profiling constructs (deeply nested slicing, conditional constraints, complex discriminators) may generate suboptimal or incomplete types.
-
-### Validation Scope
-
-- **High-level checks only**: The generated `validate()` functions execute FHIRPath expressions from profile invariants but do **not** perform:
-  - Terminology expansion or ValueSet validation
-  - Reference resolution (checking that referenced resources exist)
-  - Full cardinality enforcement for complex slicing scenarios
-  - Server-side business logic or workflow rules
-- **Use the official validator**: For production conformance testing, use the [HL7 FHIR Validator](https://github.com/hapifhir/org.hl7.fhir.core) alongside BabelFHIR-TS.
-
-### TypeScript Limitations
-
-- **Runtime type checking is limited**: TypeScript types are erased at compile time. The generated interfaces provide compile-time safety but cannot enforce constraints at runtime without the validator functions.
-- **Extension slicing**: While the generator creates typed extension interfaces, TypeScript cannot enforce that extension arrays contain exactly the required slices at compile time (this is validated at runtime).
-- **Choice types**: FHIR's `[x]` choice types (e.g., `value[x]`) are represented as union types in TypeScript, which may require runtime type narrowing.
-
-### FHIR Version Support
-
-- **R4 only**: The current version targets FHIR R4. Support for R5, DSTU2, or STU3 is not yet available.
-- **Dependencies**: Generated code depends on `@types/fhir` (R4 definitions) and `fhirpath` (R4 compatible).
-
-### Reporting Issues
-
-If you encounter an Implementation Guide that doesn't generate correctly, please [open an issue](https://github.com/quotentiroler/BabelFHIR-ts/issues) with:
-
-- The package name and version
-- The specific StructureDefinition URL
-- Expected vs. actual generated output
-- Any validation errors or type mismatches
-
-We continuously improve the generator based on real-world IG usage, and your feedback helps make BabelFHIR-TS more robust.
-
-## License
-
-ISC © Maximilian Nussbaumer
-
-## Contributing
-
-Contributions are welcome! Please read [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines on how to contribute to this project.
-
-## Security
-
-For security issues, please see [SECURITY.md](SECURITY.md) for our security policy and how to report vulnerabilities.
-
-## Links
-
-- [npm package](https://www.npmjs.com/package/babelfhir-ts)
-- [GitHub repository](https://github.com/quotentiroler/BabelFHIR-ts)
-- [Issue tracker](https://github.com/quotentiroler/BabelFHIR-ts/issues)
-- [Changelog](CHANGELOG.md)
+<div align="center">
+  <img src="./logo.png" alt="BabelFHIR-TS Logo" width="200"/>
+</div>
+
+# BabelFHIR-TS
+
+[![npm version](https://img.shields.io/npm/v/babelfhir-ts.svg)](https://www.npmjs.com/package/babelfhir-ts)
+[![License: ISC](https://img.shields.io/badge/License-ISC-blue.svg)](https://opensource.org/licenses/ISC)
+[![TypeScript](https://img.shields.io/badge/TypeScript-5.8-blue)](https://www.typescriptlang.org/)
+[![Node.js](https://img.shields.io/badge/Node.js-18%2B-green)](https://nodejs.org/)
+
+**BabelFHIR-TS** transforms FHIR® StructureDefinitions into production-ready TypeScript code with full type safety and built-in validation. Unlike generic FHIR type definitions, BabelFHIR-TS generates **profile-aware** interfaces that understand your Implementation Guide's constraints, extensions, and slicing rules.
+
+### What you get
+
+- **Strongly typed interfaces** that merge profile constraints with base FHIR types (types come from `@types/fhir`)
+- **Compiled output by default** — packages ship JavaScript (`.js`) plus TypeScript declarations (`.d.ts`)
+- **Runtime validation** using FHIRPath expressions from the profile—no external validator required for basic checks
+- **Type-safe extension handling** with proper slicing and nested extension support
+- **Random data builders** for testing and development (when class generation is enabled)
+- **Zero manual mapping**—consume any FHIR package or Implementation Guide directly from registries
+- **Fast and lightweight**—minimal runtime deps; only `fhirpath` is required for validators
+- **Install any FHIR profile as a node module**—use `babelfhir-ts install` to add Implementation Guides directly to your project
+
+## Installation
+
+Install globally (recommended when using the CLI frequently):
+
+```bash
+npm install -g babelfhir-ts
+```
+
+Or invoke on-demand without a global install:
+
+```bash
+npx babelfhir-ts --help
+```
+
+> **Requirements:** Node.js 18+ (ESM support) and an internet connection when downloading packages from remote registries.
+
+## Quick start
+
+Generate code from a local folder that contains FHIR packages:
+
+```bash
+babelfhir-ts input/ output/
+```
+
+Process a single package archive and write the generated interfaces back into a new `.tgz` file:
+
+```bash
+babelfhir-ts hl7.fhir.us.core-8.0.0.tgz us-core-generated.tgz
+```
+
+Download and process a package directly from a registry (defaults to `https://packages.simplifier.net`):
+
+```bash
+babelfhir-ts --package hl7.fhir.us.core@8.0.0
+```
+
+Download, pocess and install a processed package into your current project:
+
+```bash
+babelfhir-ts install hl7.fhir.us.core@8.0.0
+```
+
+After generation you can import the emitted classes:
+
+```ts
+import { USCorePatientClass } from "./output/USCorePatientClass";
+
+const patient = USCorePatientClass.random();
+const { errors, warnings } = await patient.validate();
+```
+
+## Using the generated code in your project
+
+Generated profile packages installed via `babelfhir-ts install` are published as **compiled JavaScript with TypeScript declarations**:
+
+- JavaScript for runtime: `index.js`, `*.js`
+- Type declarations for IDE/TS: `index.d.ts`, `*.d.ts`
+- Dependencies:
+  - `@types/fhir` is included as a dependency of the generated package (no extra setup in your app)
+  - `fhirpath` is a peer dependency (required only if you use the generated validators/classes)
+
+Install `fhirpath` in your app if you plan to call `.validate()` or use the generated classes.
+
+### Module resolution
+
+Generated packages work with all modern TypeScript setups:
+
+- **Node.js 18+** with `"type": "module"` in `package.json`
+- **Bundlers** (Vite, esbuild, Webpack) with ESM output
+- **TypeScript 5.0+** with any module resolution (`node16`, `nodenext`, or `bundler`)
+
+#### FHIR type imports
+
+Generated code imports base FHIR types from `"fhir/r4"`:
+
+```ts
+import { Appointment, Extension, CodeableConcept } from "fhir/r4";
+```
+
+Since `@types/fhir` doesn't provide a `package.json` `exports` field, BabelFHIR-TS includes an **ambient module declaration** (`fhir-r4.d.ts`) in every generated package. The generated `index.d.ts` references this file:
+
+```ts
+/// <reference path="./fhir-r4.d.ts" />
+```
+
+This ensures TypeScript can resolve `fhir/r4` imports automatically without any configuration in your project's `tsconfig.json`.
+
+## CLI reference
+
+```
+babelfhir-ts [options] [<input> [output]]
+```
+
+| Argument / option           | Description                                                                                                                                                         |
+| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `<input>`                 | Directory of FHIR packages/StructureDefinitions, single package (`.tgz`/`.zip`), or single StructureDefinition `.json`. Defaults to `./input` when omitted. |
+| `<output>`                | Destination directory or archive. Defaults to `./output` when omitted.                                                                                            |
+| `install`                 | Downloads, processes, and installs a package as a project dependency.                                                                                               |
+| `--package <pkg@version>` | Fetch a package from a registry and process it without manual download.                                                                                             |
+| `--registry <url>`        | Custom registry base URL (default:`https://packages.simplifier.net`).                                                                                             |
+| `--log <level>`           | Control logging output:`none` (default), `console`, or `file`.                                                                                                |
+| `--no-cache`              | Remove the `.cache` directory once generation completes.                                                                                                          |
+| `--no-classes`            | Skip emitting helper classes (interfaces & validators only).                                                                                                        |
+| `-h, --help`              | Print usage help.                                                                                                                                                   |
+| `-v, --version`           | Print the BabelFHIR-TS version.                                                                                                                                     |
+
+### Supported inputs
+
+- **Directory** – scan all `.tgz`, `.zip`, or `.json` files inside the folder
+- **Archive** – process a FHIR NPM package in `.tgz` or `.zip` format
+- **StructureDefinition JSON** – generate code for a single profile definitio
+
+## Scripts for contributors
+
+| Script                         | Purpose                                                                      |
+| ------------------------------ | ---------------------------------------------------------------------------- |
+| `npm run generate`           | Execute the CLI against the local `input/` folder and refresh `output/`. |
+| `npm run generate:check`     | End-to-end check: generate, type-check, and lint the emitted output.         |
+| `npm test`                   | Type-check and run all Vitest suites (coverage enabled).                     |
+| `npm run download-validator` | Fetch the official HL7 validation jar used for parity testing.               |
+
+## Caching notes
+
+The generator caches downloaded StructureDefinitions and packages inside `.cache/`. When you need a clean run, pass `--no-cache` or manually remove the folder. Temporary downloads land in `.temp-*` directories and are cleaned up automatically.
+
+## Why BabelFHIR-TS?
+
+**The FHIR Challenge**: Implementation Guides define strict profiles that constrain base FHIR resources with required or must-support elements, custom extensions, value set bindings, and cardinality rules. Existing TypeScript libraries can't capture these requirements when you need profile-specific types, leading to an overhead when using TypeScript to build apps that interact with FHIR servers.
+
+**The BabelFHIR-TS Solution**: Automatically generates TypeScript interfaces and validation logic directly from StructureDefinition JSON. Your IDE autocompletes required fields, flags missing extensions at compile-time, and validates FHIRPath invariants at runtime.
+
+## Limitations
+
+BabelFHIR-TS is a code generation tool that parses FHIR StructureDefinitions and produces TypeScript interfaces and validators. While it handles many common FHIR profiling patterns, there are important limitations to be aware of:
+
+### Profile Mapping Accuracy
+
+- **Not guaranteed for all IGs**: The generator uses heuristics to interpret StructureDefinition constraints, slicing rules, and extensions. Complex or unusual profiling patterns may not map correctly to TypeScript.
+- **Test before production**: Always validate the generated code against your specific Implementation Guide's examples and test cases. We recommend running the official FHIR validator alongside BabelFHIR-TS in your QA pipeline.
+- **Edge cases**: Rare profiling constructs (deeply nested slicing, conditional constraints, complex discriminators) may generate suboptimal or incomplete types.
+
+### Validation Scope
+
+- **High-level checks only**: The generated `validate()` functions execute FHIRPath expressions from profile invariants but do **not** perform:
+  - Terminology expansion or ValueSet validation
+  - Reference resolution (checking that referenced resources exist)
+  - Full cardinality enforcement for complex slicing scenarios
+  - Server-side business logic or workflow rules
+- **Use the official validator**: For production conformance testing, use the [HL7 FHIR Validator](https://github.com/hapifhir/org.hl7.fhir.core) alongside BabelFHIR-TS.
+
+### TypeScript Limitations
+
+- **Runtime type checking is limited**: TypeScript types are erased at compile time. The generated interfaces provide compile-time safety but cannot enforce constraints at runtime without the validator functions.
+- **Extension slicing**: While the generator creates typed extension interfaces, TypeScript cannot enforce that extension arrays contain exactly the required slices at compile time (this is validated at runtime).
+- **Choice types**: FHIR's `[x]` choice types (e.g., `value[x]`) are represented as union types in TypeScript, which may require runtime type narrowing.
+
+### Generated Helper Methods
+
+- **`random()` is not fully conformant**: The generated `.random()` methods create test data that satisfies TypeScript types and basic cardinality, but **do not guarantee** fully valid FHIR resources. Random data may violate:
+  - Complex FHIRPath invariants
+  - ValueSet bindings (codes are randomly chosen from required bindings but not guaranteed to be semantically correct)
+  - Profile-specific business rules
+  - Reference integrity constraints
+  
+  Use `random()` for development, testing, and prototyping, but always validate production data on the FHIR server side.
+
+- **`validate()` parity**: The generated validation methods execute FHIRPath expressions and check constraints from StructureDefinitions, but are **only guaranteed to match** the Firely .NET SDK validator for scenarios covered by our test suite (see GitHub actions). Edge cases, complex slicing patterns, or profiles not in our test pipeline may produce different results. For production conformance testing, use the [HL7 FHIR Validator](https://github.com/hapifhir/org.hl7.fhir.core) or [Firely .NET SDK](https://fire.ly/products/firely-net-sdk/) as the source of truth.
+
+### FHIR Version Support
+
+- **R4 only**: The current version targets FHIR R4. Support for R5, DSTU2, or STU3 is not yet available.
+- **Dependencies**: Generated code depends on `@types/fhir` (R4 definitions) and `fhirpath` (R4 compatible).
+
+### Reporting Issues
+
+If you encounter an Implementation Guide that doesn't generate correctly, please [open an issue](https://github.com/quotentiroler/BabelFHIR-ts/issues) with:
+
+- The package name and version
+- The specific StructureDefinition URL
+- Expected vs. actual generated output
+- Any validation errors or type mismatches
+
+We continuously improve the generator based on real-world IG usage, and your feedback helps make BabelFHIR-TS more robust.
+
+## License
+
+ISC © Maximilian Nussbaumer
+
+## Contributing
+
+Contributions are welcome! Please read [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines on how to contribute to this project.
+
+## Security
+
+For security issues, please see [SECURITY.md](SECURITY.md) for our security policy and how to report vulnerabilities.
+
+## Links
+
+- [npm package](https://www.npmjs.com/package/babelfhir-ts)
+- [GitHub repository](https://github.com/quotentiroler/BabelFHIR-ts)
+- [Issue tracker](https://github.com/quotentiroler/BabelFHIR-ts/issues)
+- [Changelog](CHANGELOG.md)

package/bin/babelfhir-ts.js

@@ -1,29 +1,29 @@
-#!/usr/bin/env node
-
-import { spawn } from 'child_process';
-import { fileURLToPath } from 'url';
-import { dirname, join } from 'path';
-import process from 'process';
-import fs from 'fs';
-
-const __filename = fileURLToPath(import.meta.url);
-const __dirname = dirname(__filename);
-
-// Use node directly to run the compiled JavaScript
-const mainJsPath = join(__dirname, '..', 'out', 'main.js');
-
-// Check if the compiled file exists
-if (!fs.existsSync(mainJsPath)) {
-  console.error('Compiled main.js not found. Please ensure the package was built correctly.');
-  process.exit(1);
-}
-
-const child = spawn('node', [mainJsPath, ...process.argv.slice(2)], {
-  stdio: 'inherit',
-  cwd: process.cwd(),  // Use the current working directory where the command was invoked
-  shell: process.platform === 'win32'
-});
-
-child.on('exit', (code) => {
-  process.exit(code || 0);
+#!/usr/bin/env node
+
+import { spawn } from 'child_process';
+import { fileURLToPath } from 'url';
+import { dirname, join } from 'path';
+import process from 'process';
+import fs from 'fs';
+
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = dirname(__filename);
+
+// Use node directly to run the compiled JavaScript
+const mainJsPath = join(__dirname, '..', 'out', 'main.js');
+
+// Check if the compiled file exists
+if (!fs.existsSync(mainJsPath)) {
+  console.error('Compiled main.js not found. Please ensure the package was built correctly.');
+  process.exit(1);
+}
+
+const child = spawn('node', [mainJsPath, ...process.argv.slice(2)], {
+  stdio: 'inherit',
+  cwd: process.cwd(),  // Use the current working directory where the command was invoked
+  shell: process.platform === 'win32'
+});
+
+child.on('exit', (code) => {
+  process.exit(code || 0);
 });