I am going to repeat this 3 times in the hopes that it lands, because people keep missing this despite the author emphasizing this point multiple times:
Real time type inference, editor feedback, Intellisense, is completely equivalent to using TS files.
Real time type inference, editor feedback, Intellisense, is completely equivalent to using TS files.
Real time type inference, editor feedback, Intellisense, is completely equivalent to using TS files.
There is no need to run TSC to see the type errors, in VSCode and Jetbrains editors, Typescript Language Server works with both TS files and JSDocs in JS files, in the EXACT same way, to provide this live feedback, all you need it to set allowJs and checkJs to true in your tsconfig for that to happen. There is 0 difference. ZERO. There is no need to run tsc --noEmit during dev to lint, because you get the feedback immediately in your editor just like you would if you were using TS files.
I am going to repeat this 3 times in the hopes that it lands, because people keep missing this despite the author emphasizing this point multiple times:
Real time type inference, editor feedback, Intellisense, is completely equivalent to using TS files.
Real time type inference, editor feedback, Intellisense, is completely equivalent to using TS files.
Real time type inference, editor feedback, Intellisense, is completely equivalent to using TS files.
There is no need to run TSC to see the type errors, in VSCode and Jetbrains editors, Typescript Language Server works with both TS files and JSDocs in JS files, in the EXACT same way, to provide this live feedback, all you need it to set allowJs and checkJs to true in your tsconfig for that to happen. There is 0 difference. ZERO. There is no need to run tsc --noEmit during dev to lint, because you get the feedback immediately in your editor just like you would if you were using TS files.
You run tsc as a linter.