This version 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.
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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
eslint just published its new version 3.16.0.
This version 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. 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
sourceCode.getTokenAfter
shouldn't skip tokens after comments (#8055) (Toru Nagashima)The new version differs by 1183 commits .
3c26a59
3.16.0
5bdb960
Build: package.json and changelog update for 3.16.0
d89d0b4
Update: fix quotes false negative for string literals as template tags (#8107)
21be366
Chore: Ensuring eslint:recommended rules are sorted. (#8106)
360dbe4
Update: Improve error message when extend config missing (fixes #6115) (#8100)
f62a724
Chore: use updated token iterator methods (#8103)
daf6f26
Fix: check output in RuleTester when errors is a number (fixes #7640) (#8097)
cfb65c5
Update: make no-lone-blocks report blocks in switch cases (fixes #8047) (#8062)
290fb1f
Update: Add includeComments to getTokenByRangeStart (fixes #8068) (#8069)
ff066dc
Chore: Incorrect source code test text (#8096)
14d146d
Docs: Clarify --ext only works with directories (fixes #7939) (#8095)
013a454
Docs: Add TSC meeting quorum requirement (#8086)
7516303
Fix:
sourceCode.getTokenAfter
shouldn't skip tokens after comments (#8055)c53e034
Fix: unicode-bom fixer insert BOM in appropriate location (fixes #8083) (#8084)
55ac302
Chore: fix the timing to define rules for tests (#8082)
There are 250 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.