Update typescript-eslint-parser to version 3.0.0 🚀 #836
Conversation
This file contains 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
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.
Hello lovely humans,
typescript-eslint-parser just published its new version 3.0.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 typescript-eslint-parser.
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 ✨
You rock!
🌴
GitHub Release
instanceofto ast-converter (fixes #252) (#251) (Danny Arnold)The new version differs by 25 commits .
69edd793.0.026905f1Build: changelog update for 3.0.06b56bfeFix: Use correct starting range and loc for JSXText tokens (fixes #227) (#271)f5fcc87Breaking: Allow comment scanner to rescan tokens (fixes #216) (#219)f836bb9Chore: Refactor the codebase (fixes #220) (#261)aade6bdChore: Update README with list of known issues (#247)c8e881aBreaking: Normalize type parameters (fixes #197) (#196)d37bf04Fix: Type parameter start location calculation (fixes #260) (#259)1a97650Fix: Handle case where class has extends but no super class (fixes #249) (#254)00ad71dFix: addinstanceofto ast-converter (fixes #252) (#251)2989f8bUpgrade: Update semver package (#246)b1efe69Breaking: Change how interface node gets converted (fixes #201) (#241)e311620Fix: Set await property on async iterators (for await) (fixes #236) (#239)a294afaFix: Set async on async FunctionExpressions (fixes #244) (#245)7c00f16Chore: Add tests for object spread and async generator (refs #236) (#237)There are 25 commits in total. See the full diff.