feat: update eslint-plugin-node + update configs
#24
Conversation
Codecov ReportBase: 97.17% // Head: 97.17% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #24 +/- ##
=======================================
Coverage 97.17% 97.17%
=======================================
Files 39 39
Lines 390 390
=======================================
Hits 379 379
Misses 11 11 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
|
@eslint-community/eslint-tsc @eslint-community/core-team @eslint-community/mysticatea-eslint-plugin Since this plugin is adhering the same semantic versioning policy as ESLint, adding new rules to a plugin would be a breaking change, so this PR would need to be released in a major release I guess? |
MichaelDeBoey
force-pushed
the
patch-10
branch
from
47a72e2 to
dd84984
Compare
BREAKING CHANGE: `+node`, `es5`, `es2015`, `es2016`, `es2017`, `es2018`, `es2019`, `es2020`, `es2021` & `es2022` configs now have extra rules from `eslint-plugin-node`
MichaelDeBoey
force-pushed
the
patch-10
branch
from
dd84984 to
d3357e6
Compare
|
🎉 This PR is included in version 15.0.0-alpha.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 15.0.0-beta.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 15.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Re-submission of mysticatea#42
BREAKING CHANGE:
+node,es5,es2015,es2016,es2017,es2018,es2019,es2020,es2021&es2022configs now have extra rules fromeslint-plugin-node