Update esprima to the latest version 🚀 #21
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 4.0.0 of esprima just got published.
The version 4.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 esprima.
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.
Commits
The new version differs by 102 commits ahead by 102, behind by 30.
56c0f0fStable version 4.0.0d95fac6Update ChangeLog for 4.0.00640979Update README.md to prepare for version 4.0e3df3f5Travis CI and AppVeyor: Run with Node.js v892fac13Fix the "tokens" and "comment" argument namesa8bd8efUpdate TypeScript-related dependencies304ba69Use const whenever possible02788f6Improve error message upon an invalid JSX elementcc95d4cJSX: Matching a token should not be too strict93ce59dAllowinexpression in a concise body with a function body211d6c2Allow JSX element in a yield expressionf4f22a0Downstream tests: run them with Node.js v6.1c5fee53Fix the documentation for the AST of ForStatementb57c2f4Use access modifier in the Scanner classeab4c1fPure tokenizer: simplify the choice of obtaining a new tokenThere are 102 commits in total.
See 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 🌴