Codelyzer does not work with Typescript@next (2.1.0)
See original GitHub issueWe 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:
Error: Unsupported TypeScript version: 2.1.0-dev.20160725
at Object.current (D:\...\node_modules\codelyzer\util\syntaxKind.js:1796:23)
at ClassMetadataWalker.visitClassDeclaration (D:\...\node_modules\codelyzer\useLifeCycleInterfaceRule.js:40:37)
at ClassMetadataWalker.SyntaxWalker.visitNode (D:\...\node_modules\tslint\lib\language\walker\syntaxWalker.js:264:22)
at D:\...\node_modules\tslint\lib\language\walker\syntaxWalker.js:459:63
at visitEachNode (D:\...\node_modules\typescript\lib\typescript.js:8115:30)
at Object.forEachChild (D:\...\node_modules\typescript\lib\typescript.js:8273:24)
at ClassMetadataWalker.SyntaxWalker.walkChildren (D:\...\node_modules\tslint\lib\language\walker\syntaxWalker.js:459:12)
at ClassMetadataWalker.SyntaxWalker.visitSourceFile (D:\...\node_modules\tslint\lib\language\walker\syntaxWalker.js:190:14)
at ClassMetadataWalker.SyntaxWalker.visitNode (D:\...\node_modules\tslint\lib\language\walker\syntaxWalker.js:414:22)
at ClassMetadataWalker.SyntaxWalker.walk (D:\...\node_modules\tslint\lib\language\walker\syntaxWalker.js:7:14)
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "c:\\Program Files\\nodejs\\node.exe" "C:\\Users\\...\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "tslint"
npm ERR! node v6.3.1
npm ERR! npm v3.10.6
npm ERR! code ELIFECYCLE
npm ERR! ...@...-SNAPSHOT tslint: `tslint -c ./node_modules/.../tslint.json --force ./app/**/*.ts`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ...@...-SNAPSHOT tslint script 'tslint -c ./node_modules/.../tslint.json --force ./app/**/*.ts'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ... package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! tslint -c ./node_modules/.../tslint.json --force ./app/**/*.ts
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs ...
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls ...
npm ERR! There is likely additional logging output above.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
codelyzer - npm
codelyzer. A set of tslint rules for static code analysis of Angular TypeScript projects. (If you are using ESLint check out the new ......
Read more >tslint-multi - npm Package Health Analysis - Snyk
typescript is a peer dependency of tslint . This allows you to update the compiler independently from the linter. This also means that...
Read more >tslint | Yarn - Package Manager
This means that some rules that previously worked without the type checker now require it. This includes: no-unused-variable; no-use-before-declare. This breaks ...
Read more >property does not exist on type 'typeof import dynamic import
The dynamic import returns the module, not the element, as there can be ... 2.0.0 and Angular Material 2.0.0-alpha.8-2 , the imports now...
Read more >codelyzer versions and peer dependencies - NPM Peer
The table below has a list of all versions of codelyzer with compatible (peer) dependencies. Filter by. e.g: 12.x, 1.2.7. - OR -....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@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.
@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.