Update eslint-plugin-node to the latest version 🚀 #17
Conversation
This file contains 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
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Version 5.0.0 just got published.Update to this version instead 🚀 Release Notesv5.0.0Notable changes are 2:
Breaking changes
New rules
Bug fixes |
Version 5.1.0 just got published.Update to this version instead 🚀 Release Notesv5.1.0Enhancements
|
Version 5.1.1 just got published. |
Version 5.2.0 just got published.Update to this version instead 🚀 Release Notesv5.2.0Bug fixes
|
Version 5.2.1 just got published. |
Version 6.0.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 9 commits.
See the full diff |
Version 6.0.1 just got published.Update to this version instead 🚀 Release Notesv6.0.1Bug fixes
|
Version 7.0.0 just got published.Update to this version instead 🚀 Release Notesv7.0.0Breaking changes
New rules
Deprecated rules
ChoreI extracted the logic which detects certain globals and modules and those properties to the eslint-utils package. I wish it to be useful for your ESLint plugins. All commits: 5260039...890ee63 CommitsThe new version differs by 48 commits.
There are 48 commits in total. See the full diff |
Version 7.0.1 just got published.Update to this version instead 🚀 Release Notesv7.0.1Bug fixes
|
Update to this version instead 🚀 Release Notes for v8.0.0This release focuses on supporting new things that were added between Node.js 8.7.0 and 11.0.0. Breaking changes
New rulesCommitsThe new version differs by 13 commits.
See the full diff |
Update to this version instead 🚀 Release Notes for v8.0.1🐛 Bug fixes
CommitsThe new version differs by 8 commits.
See the full diff |
|
|
|
|
|
|
|
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.
Version 5.0.0 of eslint-plugin-node just got published.
The version 5.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of eslint-plugin-node.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v5.0.0Notable changes are 2:
no-unpublish-importrule andno-unpublish-requirerule.Breaking changes
no-unsupported-featuresrule for Node.js 8.4.0.0if you don't specify the node version. It has been0.10.0before.SharedArrayBufferandAtomics. Currently any versions of Node.js don't support those variables.no-deprecated-apirule for Node.js 8.vm.runInDebugContext().no-unpublish-importrule andno-unpublish-requirerule.New rules
require()expressions orimportdeclarations if those import extraneous packages.no-unpublished-requireandno-unpublished-import.Bug fixes
no-unsupported-featuresaboutsemvercomparison. (#78)Commits
The new version differs by 14 commits.
56347185.0.0aea8e82Chore: remove deprecated rule's tests118a1deChore: add note aboutrequire("punycode/")(fixes #72)cf36e6dChore: improve auto-generation scriptd4e6bc4Breaking: remove extraneous check fromno-unpublish-*(fixes #71)a75c638New:no-extraneous-*rules (refs #71)deb4f55Fix:no-unsupported-featuresgoes wrong on>=7.10.0(fixes #78)0e487f9Breaking: updateno-deprecated-api(fixes #80)3387336Breaking: updateno-unsupported-featuresrule (fixes #79)fdd7877Chore: add Node.js 8 to CIfa95be2Chore: add cache to exists()ffc7fcbChore: refactor with classes.8f00ebbChore: remove object-assign from dependencies734d2e7Chore: upgrade dependenciesSee the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴