fix(create): Resolve ERR_REQUIRE_ESM error for chalk/ora #359
Open
SabaliDev wants to merge 1 commit into
Open
Conversation
👷 Deploy request for celo-composer pending review.Visit the deploys page to approve it
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The create command was failing with an ERR_REQUIRE_ESM error when executed via npx. This issue stemmed from the use of static require() imports for chalk and ora, both of which are now published as pure ES Modules.
This commit refactors the code to use dynamic import() for these dependencies, which is the correct and compatible approach when loading ESM packages in a CommonJS context. This resolves the runtime error and restores functionality when running the CLI via npx.
Fixes #358