Closed KingOfTac closed 2 months ago
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.isStringLiteral
etc
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
Checklist
--dev
flag to get more information?Currently, it looks like the analyzer is using typescript@4.3.2 internally. AST Explorer now uses typescript@4.7.4 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 aVariableStatement
and in the analyzer it is aWhileStatement
.