We'll probably have to do type checking and not just compilation. @timer had some ideas for it.
timneutkens
All 4 comments
It'd be great if TypeScript errors did not block page compilation unless they are fatal. Problems like mismatching types are useful to see in the editor and when running yarn lint, however, if they crash page compilation in dev, that becomes quite annoying and blocks experimentation.
kachkaev
on 23 Apr 2019
👎4
👍4
I see @Timer closed #7125. What's the latest on this?
isaachinman
on 2 May 2019
This has been implemented!
Timer
on 8 May 2019
🎉1
I created a new issue out of the comment above: https://github.com/zeit/next.js/issues/7687
kachkaev
on 27 Jun 2019
Was this page helpful?
0 / 5 - 0 ratings
Related issues
YarivGilad
路
3Comments
pie6k
路
3Comments
formula349
路
3Comments
timneutkens
路
3Comments
jesselee34
路
3Comments
Most helpful comment
It'd be great if TypeScript errors did not block page compilation unless they are fatal. Problems like mismatching types are useful to see in the editor and when running
yarn lint, however, if they crash page compilation in dev, that becomes quite annoying and blocks experimentation.