| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
This creates 1217 files. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
Commit 2 and 3 could be reverted after AsyncIterators are added to ESlint itself. |
Sorry, something went wrong.
Agree with @MylesBorins's comment. Don't want to start a big bikeshed on this PR, but in theory if this lands, so should #17320, which is very similar in nature. |
Sorry, something went wrong.
|
Why do we want to add babel-eslint as the parser? (Not objecting, of course, but I do want to understand the motivation!) |
Sorry, something went wrong.
|
To support async-iterators. They are curreny a stage 3 proposal, and it’s not supported into eslint yet. |
Sorry, something went wrong.
There was a problem hiding this comment.
Rubberstamp lgtm after checking out and seeing things work.
Sorry, something went wrong.
Sorry, something went wrong.
|
According to https://twitter.com/geteslint/status/944829414159810560, there is an issue with babel-eslint and eslint 1.14.0. The issue appears fixed with babel-eslint 8.1.0. Assuming that we'll eventually update to 1.14.0+, it might make sense to update to both of those versions now. I'm also not big on adding this to the repo, although I won't block this either. Even if we remove them later, they will still be part of the git history. |
Sorry, something went wrong.
|
I also don't like having to add this dependency, but do we have an alternative? This will be necessary for import.meta as well. BTW 1054 of the new files come from lodash :( |
Sorry, something went wrong.
No, if we want to experiment with the new language feature in node core before they are finalyzed. Is there anyone objecting landing this? |
Sorry, something went wrong.
Would git submodules work here? |
Sorry, something went wrong.
|
Added a commit to update ESLint to 4.14.0 and updated babel-eslint to the latest version. |
Sorry, something went wrong.
|
Are we ok to land this? cc @nodejs/tsc |
Sorry, something went wrong.
There was a problem hiding this comment.
Still LGTM
Sorry, something went wrong.
|
It looks like the merge of master is making CI unhappy. Let me rebase this properly. |
Sorry, something went wrong.
|
Updated |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
@targos the older CI I started looks good from what I can tell, everything that is unstable is also unstable on other builds unrelated to the PR. |
Sorry, something went wrong.
|
@benjamingr Oh, sorry my tab was not up-to-date. I didn't see your message. I stopped my run. |
Sorry, something went wrong.
Sorry, something went wrong.
|
Does this need to land on v9.x? |
Sorry, something went wrong.
This is required because we need to add the babel-eslint dependency and it has to be able to resolve "eslint". babel-eslint is required to support future ES features such as async iterators and import.meta. Refs: #17755 PR-URL: #17820 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
PR-URL: #17820 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
This is required because we need to add the babel-eslint dependency and it has to be able to resolve "eslint". babel-eslint is required to support future ES features such as async iterators and import.meta. Refs: #17755 PR-URL: #17820 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
PR-URL: #17820 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Create tools/update-babel-eslint.sh script and execute it to do the first installation of the package. Update tools/license-builder.sh and execute it to add babel-eslint's license to our LICENSE file. PR-URL: #17820 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
PR-URL: #17820 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
|
Should we backport this to v6.x or v8.x? |
Sorry, something went wrong.
PR-URL: nodejs#19287 Refs: nodejs#17820 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
|
If this gets backported it should come with #19287 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Commit 1:
Commit 2:
Commit 3:
Checklist
Affected core subsystem(s)
tools
/cc @mcollina