custom-elements-manifest
custom-elements-manifest copied to clipboard
update included typescript version
Checklist
- [x] Did you run the analyzer with the
--devflag to get more information? - [ ] Did you create a minimal reproduction in the playground?
Currently, it looks like the analyzer is using [email protected] internally. AST Explorer now uses [email protected] which has made developing plugins a bit difficult due to typescript internal interfaces changing across versions. An example of this is in the SyntaxKind enum. In AST Explorer a node kind of 237 is a VariableStatement and in the analyzer it is a WhileStatement.
yeah you shouldnt really check for SyntaxKind like that I dont think, you should use the methods provided by TS, like ts.isStringLiteral etc
yeah you shouldnt really check for SyntaxKind like that I dont think, you should use the methods provided by TS, like
ts.isStringLiteraletc
Makes sense, thanks. One other thing I have run up against with the version bundled with the analyzer is that it looks like it doesn't associate jsDoc comments with variable declarations while newer versions of the language do.
Ts version was updated in 0.9.4