-
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v16 planned changes #42
Comments
What's the rationale to setting |
Regarding
As far as which coverage level of ecmaScript to go with, I guess that could be up for debate. Maybe a strict/loose scenario? |
I'm interested in tackling TypeScript conversion but it shouldn't be a breaking change if it's precompiled to CJS. Would you be open to a pull request? |
I would personally prefer typing up the existing code rather than converting it to TypeScript. TypeScript works just as well on type annotated JS code as it does on TS code gut the latter requires a new compilation step? |
Types would be nice but the bigger benefit for me is ESM. The export style in this codebase was a little difficult to read so updating those would be a huge improvement. Compilation step would be necessary but can be seamless and instantaneous using esbuild. |
Any update on this? There are some PRs like #87 pending to this. Also Node.js 14 will get EOL in one month, we should remove support for it too. |
node.js < 13, v15 has been eol. and node.js v14 will be eol in a few months. refs: #42
node.js < 13, v15 has been eol. and node.js v14 will be eol in a few months. refs: #42
node.js < 13, v15 has been eol. and node.js v14 will be eol in a few months. refs: #42
node.js < 13, v15 has been eol. and node.js v14 will be eol in a few months. refs: #42
* feat!: engines.node defaults to 16.0.0 node.js < 13, v15 has been eol. and node.js v14 will be eol in a few months. refs: #42 * docs: update docs to reflect the new default version * docs: deduplication of the configured Node.js version range * docs: fix node lts statement
according to node.green, Node.js 16.0.0 supports all ES2021 features. refs: #42
according to node.green, Node.js 16.0.0 supports all ES2021 features. refs: #42
Starting a list of my desired breaking changes, feedback welcome. We can perform this release once we have compiled enough changes. We should watch out for any breaking changes needed for ESLint v9 in the coming months.
Planned:
recommended
changeseslint.config.js
: feat: support the new eslint config. #89Maybe:
The text was updated successfully, but these errors were encountered: