-
Notifications
You must be signed in to change notification settings - Fork 235
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
Codelyzer does not work with Typescript@next (2.1.0) #72
Comments
When I fix the source else if (/2\.1\..*/.test(ts.version)) {
cachedKinds = SyntaxKind_2_0;
} |
Hey @httpdigest it is kind of risky to use a fix like the one you provided because we're not sure the syntax tokens have the same values. I'll fix this issue in a couple of days. |
Any news on this? (Same issue with any version >= 2.0.0) |
@jppellerin should be working for 2.0.0. Are you using 0.0.26? I'll fix it for >2.0.0 in the next week. |
@mgechev : Yup... user error on that one. Apologies. Not sure why it didn't upgrade with ^0.0.23... but forced it to 0.0.26 and it worked. Thank you. |
Is this still being worked on? Using codelyzer with TypeScript 2.1.0-* does not work with the following error message (as mentioned in the first post of this issue):
|
Should be fixed in the next a couple of days and released together with the template support. |
We currently need typescript@next to have a bug with Promise.all fixed (among others). But codelyzer does not work with that Typescript version:
The following error message is printed:
The text was updated successfully, but these errors were encountered: