Re:Svelte is migrating from TypeScript to JSDoc
by rich_harris on Wednesday May 10, 2023 @03:27PM
(#35892262)
You are making judgements based on a draft PR. There is a ton of work still to do.
Re:Svelte is migrating from TypeScript to JSDoc
by Rapzid on Wednesday May 10, 2023 @03:36PM
(#35892401)
> There is a ton of work still to do.
What's the estimated ROI?
Re:Svelte is migrating from TypeScript to JSDoc
by postalrat on Wednesday May 10, 2023 @03:44PM
(#35892495)
That depends on how much you value getting a bunch of developers to think about svelte, jsdoc, and typescript.
Re:Svelte is migrating from TypeScript to JSDoc
by bilalq on Wednesday May 10, 2023 @03:32PM
(#35892345)
Fair enough! I'd love to read a blog post about this after you finish the work.
Re:Svelte is migrating from TypeScript to JSDoc
by myvoiceismypass on Wednesday May 10, 2023 @04:13PM
(#35892828)
Maybe I am unfamiliar with jsdoc, or what the shape of Node from acorn is, but yeah if every function is returning any, that seems like a big downgrade and sacrifice.
Re:Svelte is migrating from TypeScript to JSDoc
by _gruntled on Wednesday May 10, 2023 @05:41PM
(#35893903)
We're using an automated tool to do the gross conversion, then combing through fixing the issues. There's a reason the PR's a draft, dammit! :lol: Don't worry, _no_ type-safety will be lost, internally or externally.
Before:
After: But I'm not a Svelte maintainer or user, so if this is their choice, I guess it is what it is. It's not something I'd ever consider. There are other approaches for making linked npm package workflows more manageable. There's the one mentioned by one of the VSCode maintainer, but the simplest setup is to just have a watch process running that recompiles on the fly.