fix: use dynamic import() in npm check script for ESM compatibility#106
Merged
Conversation
…105) The package declares "type": "module" so Node 20+ rejected the require() call with ERR_REQUIRE_ESM, causing npm run check to fail before parsing any files.
nawforce
approved these changes
Apr 26, 2026
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
2 participants
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.
Summary
npm/package.jsondeclares"type": "module", so Node 20+ rejected therequire()call in thecheckscript withERR_REQUIRE_ESM. Switched to dynamicimport()which works in both CJS and ESM contexts.Test plan
npm run checkruns successfully (parses 0 .cls/.trigger/.apex files in the npm dir, as expected)