Use native node for release script & eslint config instead of tsx/jiti#541
Open
Use native node for release script & eslint config instead of tsx/jiti#541
Conversation
b5c1d2a to
bd0ddb0
Compare
bd0ddb0 to
149ff45
Compare
149ff45 to
e359f2e
Compare
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
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.
Type-stripping is stable and unflagged in Node
>=22.18.0.Currently ESLint requires an experiment flag to use native Node type-stripping to load the config file, despite Node type-stripping not being experimental anymore. Hopefully this is resolved soon.
unstable_native_nodejs_ts_configafter Node.js v22.18.0 / v24.3.0 eslint/eslint#19985The
devEnginesfield inpackage.jsonenforces runtime requirements for dev environments (ex: the minimum node version necessary to runeslint).