You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
>.\node_modules\.bin\rollup --config
index.ts → ....
[!] (plugin typescript) TypeError: Cannot read property 'kind' of undefined
index.ts
TypeError: Cannot read property 'kind' of undefined
at visitObjectLiteralExpression (C:\test\node_modules\typescript\lib\typescript.js:80338:35)
at visitJavaScript (C:\test\node_modules\typescript\lib\typescript.js:78758:28)
at visitor (C:\test\node_modules\typescript\lib\typescript.js:78701:24)
at Object.visitNode (C:\test\node_modules\typescript\lib\typescript.js:70936:23)
at flattenBindingOrAssignmentElement (C:\test\node_modules\typescript\lib\typescript.js:73016:34)
at flattenObjectBindingOrAssignmentPattern (C:\test\node_modules\typescript\lib\typescript.js:73078:21)
at flattenBindingOrAssignmentElement (C:\test\node_modules\typescript\lib\typescript.js:73028:13)
at Object.flattenDestructuringBinding (C:\test\node_modules\typescript\lib\typescript.js:72962:9)
at visitVariableDeclaration (C:\test\node_modules\typescript\lib\typescript.js:80117:30)
at Object.flatMap (C:\test\node_modules\typescript\lib\typescript.js:607:25)
Comment
If this isn't a bug in using typescript, it might be a bug in typescript itself, but I've only encountered it while using this rollup plugin. Please feel free to pass the buck to the TS team if
appropriate;-)
workaround/possible fix: in typescript.js, line 80338, protect property.name.kind by checking for property.name first.
The text was updated successfully, but these errors were encountered:
@clausreinke after running your repro it looks to me like the problem exists with typescript. I'm not a TS expert so I can't provide guidance there, but the stack trace is solely within the typescript module itself.
How Do We Reproduce?
rollup-typescript-problem.zip
Expected Behavior
compile without errors
Actual Behavior
Comment
If this isn't a bug in using
typescript
, it might be a bug intypescript
itself, but I've only encountered it while using this rollup plugin. Please feel free to pass the buck to the TS team ifappropriate;-)
workaround/possible fix: in
typescript.js
, line 80338, protectproperty.name.kind
by checking forproperty.name
first.The text was updated successfully, but these errors were encountered: