fix: use yargs main entry for node 26 compatibility#1
Merged
Conversation
The yargs/yargs subpath resolves to an extensionless file in a type: module package, which Node 26 loads as ESM. That file uses require() and throws. The yargs main entry is real CommonJS and its default export is still the callable factory.
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 yargs/yargs subpath resolves to an extensionless file in a type: module package, which Node 26 loads as ESM. That file uses require() and throws. The yargs main entry is real CommonJS and its default export is still the callable factory.