-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
tools: update to ESLint 4.8.0 #16199
Conversation
An extra space was not caught by the linter due to what appears to be a bug in eslint 4.3.0 — remove it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This changes about twice as many files as I would expect. Was ESLint updated using tools/update-eslint.sh
? If not, can you remove the commit that updates ESLint and use that instead? (And yes, that's probably not documented anywhere and should be.)
bd1fb2c
to
dfc0467
Compare
@Trott fixed now. Thanks! (This will teach me not to make a PR jet-lagged on a Friday night. 😂 I even knew that script was there.) |
Still seems to update about 70 more files than I get when I do it locally, but I suppose that might be due to different versions of npm or something like that...
@Trott I get 497 (16 more) now but eslint just released 4.9.0 so that's probably the reason for the difference. I'm using |
The difference in changed-file count might be due to updated |
An extra space was not caught by the linter due to what appears to be a bug in eslint 4.3.0 — remove it. PR-URL: nodejs#16199 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
PR-URL: nodejs#16199 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
An extra space was not caught by the linter due to what appears to be a bug in eslint 4.3.0 — remove it. PR-URL: #16199 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
PR-URL: #16199 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
An extra space was not caught by the linter due to what appears to be a bug in eslint 4.3.0 — remove it. PR-URL: nodejs/node#16199 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
PR-URL: nodejs/node#16199 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
This is going to need to be backported to v6.x Most likely it will make sense to simply update the 6.x branch directly and label this one don't land |
An extra space was not caught by the linter due to what appears to be a bug in eslint 4.3.0 — remove it. PR-URL: nodejs/node#16199 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
PR-URL: nodejs/node#16199 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Yuta Hiroto <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
The first commit addresses an extraneous space in
lib/modules.js
which seems to go unnoticed in v4.3.0 ofeslint
but gets flagged by v4.8.0. The second commit upgrades to[email protected]
. This mimics the PRs for 4.2.0 & 4.3.0 upgrades.Here's the changelog: https://github.com/eslint/eslint/blob/master/CHANGELOG.md (Quite a few bug fixes & also some perf changes so I figured it was worth upgrading)
/cc @Trott (since you did the 4.2.0 & 4.3.0 updates)
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
lib, tools