TypeError: Cannot read property 'kind' of undefined at getErrorSpanForNode
See original GitHub issueThere’s a PR open for this one.
Under some set of rituals and incantations I have not been able to replicate, tsc
throws the following error:
There’s been several bugs open - and fixed - around this.
I could not replicate, it was easier to fix. The fix addresses a simple logical inconsistency where a safety check happened after it was necessary.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
TypeError: Cannot read property 'kind' of undefined at ...
This problem started to occur when updating my Angular 6 project to 7.x. I opened an issue on the angular-cli github repo but...
Read more >react-redux-typescript-guide/Lobby - Gitter
「atl」: Child process failed to process the request: TypeError: Cannot read property 'kind' of undefined at getErrorSpanForNode ...
Read more >Toolips ng build –prod error - Material Design for Bootstrap
when I was trying to build production of my project we got this error: in Error: TypeError: Cannot read property 'kind' of undefined...
Read more >TypeError: Cannot read property 'kind' of undefined at ... - Dirask
I have got following error during my TypeScript project compilation into single file: I run my project with: tsconfig.prod.json file looks following way:...
Read more >Cannot Read Property 'Type' Of Undefined Angular 9 - ADocLib
BUILD ERROR Cannot read property 'type' of null TypeError: Cannot read property 'type' of Describe what the desired behavior would be. -->. Provide...
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 FreeTop 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
Top GitHub Comments
After some more testing
typescript@next
seems to handle the above case correctly,I believe I’m having the same issue as you having to do with legacy flow types tripping up the compiler. Typescript seems to be tripping up on
import type
statements if they appear in js files. Not sure if the pr already fixed this but here’s a more contained test case if the Needs more Info tag still applies.tsconfig.json
test.js