-
-
Notifications
You must be signed in to change notification settings - Fork 395
Update eslint to the latest version 🚀 #237
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
Closed
Closed
Conversation
This file contains hidden or 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
using the easiest solution (applying DeMorgan).
[tokenizer] don't reset comment state in case of long endings
[Tokenizer] don't reset CDATA state in case of long endings
todo: update readme
Version 2.3.1 : -> % node bench2.js htmlparser2: 01.86 ms/el Version 3.1.2 without the fix : -> % node tests/bench.js htmlparser2: 04.50 ms/el Version 3.1.2 with the fix : -> % node tests/bench.js htmlparser2: 01.75 ms/el
[tokenizer] fix perf regression
[parser] implicit open only p and br tags
Add parseDOM and parseFeed helper methods
Add link to live demo
This ensures that we catch the close tag when the special ends with a "<".
Consider "<" before checking if in a special
Fix highlighted README.md
and update a few modules
Has some nice additional features, eg. clicking on the source highlights the AST node.
* Update deps * Fix eslint * Update .travis.yml
According to the official repository of nodejs/readable-stream: If you want to guarantee a stable streams base, regardless of what version of Node you, or the users of your libraries are using, use readable-stream only and avoid the "stream" module in Node-core. Also, stream module does not exist anymore in Node 9+, breaking the library.
3 similar comments
Version 5.0.1 just got published.Update to this version instead 🚀 Release Notesv5.0.1 |
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 was just published.
[eslint](https://github.com/eslint/eslint)
The version 5.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of eslint.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v5.0.0Release blogpost
Migration guide
Commits
The new version differs by 148 commits.
36ced0a
5.0.0
5fd5632
Build: changelog update for 5.0.0
0feedfd
New: Added max-lines-per-function rule (fixes #9842) (#10188)
daefbdb
Upgrade: eslint-scope and espree to 4.0.0 (refs #10458) (#10500)
077358b
Docs: no-process-exit: recommend process.exitCode (#10478)
f93d6ff
Fix: do not fail on unknown operators from custom parsers (fixes #10475) (#10476)
05343fd
Fix: add parens for yield statement (fixes #10432) (#10468)
d477c5e
Fix: check destructuring for "no-shadow-restricted-names" (fixes #10467) (#10470)
7a7580b
Update: Add considerPropertyDescriptor option to func-name-matching (#9078)
e0a0418
Fix: crash on optional catch binding (#10429)
de4dba9
Docs: styling team members (#10460)
5e453a3
Docs: display team members in tables. (#10433)
b1895eb
Docs: Restore intentional spelling mistake (#10459)
a9da57d
5.0.0-rc.0
3ac3df6
Build: changelog update for 5.0.0-rc.0
There are 148 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴