-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Support TypeScript 3.7 (using a fork of typescript-estree) #6680
Conversation
I guess I’m fine with using your fork for now. But if so we should make it the top priority to get 2.0 out after 1.19. A non-ambitious 2.0 where we get rid of all unsupported Node.js versions and remove deprecated stuff and other small breaking changes. |
I've added this package as a dev dep with TS 3.7.0-beta but when saving |
@damiangreen Try this PR instead. If it's still reproduced, please post a snippet of your code to that PR. |
@thorn0 that fixed it thanks! |
Test code is from #6657 (by Cryrivers), replace
@typescript-eslint/typescript-estree
v2.4.0 with my fork version that works for node 4asserts
keyword (Fixes [TypeScript 3.7] add support forasserts
keyword #6574)I suggest we use my fork until prettier starting v2.0.0(will drop node 6 support #3919), since many people want Typescript 3.7 support. we can switch back anytime
Yesterday, I saw someone from
typescript-eslint
team says they may try to bring node 6 support back, hope it's true.My build script can be found on https://github.com/fisker/typescript-estree-for-node-6 , repo is a little mess now
docs/
directory)CHANGELOG.unreleased.md
file following the template.✨Try the playground for this PR✨