feat!: yargs is now ESM first #503
Draft
Conversation
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
|
The linting is out of date, and I abandoned my first try at copying setup form
@bcoe are you still keen on standard and/or gts, or should I just work on getting base eslint setup for now? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Stop shipping dual esm/cjs. Ship just esm and rely on require(esm) support in recent versions of node to support CJS users.
The main testing code "moved" from
.cjsto.mjswith minor changes, but the diff is messy because both files existed.Following yargs moving from dual CJS/ESM to ESM-only: yargs/yargs#2451