3 ms·
I am a big advocate for typescript, but I'm sympathetic to the maintainer's concerns. I've had similar concerns about how I'm complicating people's build proces
by zeroCalories 3y ago
I am a big advocate for typescript, but I'm sympathetic to the maintainer's concerns. I've had similar concerns about how I'm complicating people's build process by requiring a specific compiler. Not a huge deal for internal projects, but every org has their own idiosyncracies, and requiring typescript could become a huge pain point that leads them to drop svelte. JSDoc can work just as well without the headache, but I've found that text editors don't work as well with JSDoc type checking.
- o1y32 3y ago"Requiring a specific compiler" That happens every day in other languages. Lots of C++ projects require Visual Studio on Windows, sometimes certain other tools (e.g. https://winscp.net/forum/viewtopic.php?t=25209 https://winscp.net/forum/viewtopic.php?t=25209). Other projects expect you to use the official compiler, because almost nobody ever tried using a non official compiler with that project and how see how things would go. I don't know how it is a problem if TypeScript compiler is required (by itself).
- zeroCalories 3y agoI think we're talking about two different problems. You don't need to switch your whole project to typescript to use typescript, I'm just talking about the headache that comes from mixing something like vanilla js, webpack, closure compiler, and typescript. Vanilla js with JSDoc tends to play well with everything, so I think it's well suited for a library.