|
@sanders_n | |||||
|
Have you been looking for a low impact way to add Typescript? I wrote a tutorial:
devblogs.microsoft.com/typescript/how…
|
||||||
|
||||||
|
|
Nathan Shively-Sanders
@sanders_n
|
14. lip |
|
I use the tsconfig from the article every time I start a new JS project, so it's useful for new projects as well.
|
||
|
||
|
Kinrany
@kinrany
|
14. lip |
|
It'd be cool to view and edit JS files with JSDoc type annotations and separate .d.ts typings as if they were written in TS
|
||
|
|
||
|
|
Nathan Shively-Sanders
@sanders_n
|
24. lip |
|
The webpack people showed me a VS Code plugin that would display JSDoc in the same format as Typescript type annotations. But I can't find it online, so maybe it was just a demo? Not sure if that's what you are looking for anyway.
|
||
|
|
||
|
Tomáš Ječmen
@jecatomas
|
14. lip |
|
Nice. We also tried combination of babel and ts-loader in webpack config. You can compile js with babel, ts with ts-loader and webpack will put everything to one bundle for you. You can migrate file by file during normal development.
|
||
|
|
||
|
David Foster
@davidfstr
|
17. srp |
|
I used a similar process for gaining #TypeScript-style type checking in my own JS codebase (~200 files, ~50k lines). -- However to avoid getting swamped with errors I started with checkJs=false and added "// @ts-check" to JS files one-by-one.
|
||
|
|
||
|
Rune Jeppesen
@runjep
|
14. lip |
|
Cool. I posted a question in the blog.
|
||
|
|
||
|
Yassine Chbani
@yassineccc
|
14. lip |
|
|
||
|
Daniel Schildt
@autiomaa
|
16. lip |
|
Large part of what makes TypeScript effective is the ability to start using it incrementally. Most companies don't want to switch to new tools unless there is a visible proof that it helps with their existing applications. Step by step, improving documentation etc. allows that.
|
||
|
|
||