Compared to using plain tsc to compile the code, is that it’s a lot quicker. The compiled code has some odd conventions, like using void 0 instead of undefined, but … whatever works!
So far, it has been an easy-entry high-ROI tool that helps me publish TS/JS tools quite easily.
Currently we're using tsc with the new build mode to build everything at once, but the result is incredibly brittle and requires a lot of unnecessary extra configuration all over the place that tends to confuse people when they need to add extra packages or make changes somewhere. It's also very slow (hopefully something that will be fixed by tsgo, eventually).
My initial plan was to have a separate tsdown config in each package and use pnpm to build the entire monorepo (or at least, the parts necessary for each sub-application) in parallel. But your config also looks like a useful approach, I'll explore that as well. Thanks for sharing!
JimDabell•2h ago
The “What is tsdown” link goes to a video with pre-roll ads.
I put the video URL into Gemini and asked it what it does. Gemini hallucinated a comparison with Rspack.
I followed the link to documentation from the YouTube description and it took me back to the main page that does not have a description of what it does.
There is an FAQ with a single question:
> Will tsdown support stub mode (similar to unbuild)?
Is there any kind of text description available for what this is and why I – as somebody who is currently writing a lot of front-end code – should care?
typpilol•2h ago
But again, all it says is it's fast. And vite is pretty damn fast and widely supported so?
Plus vite exposes roll down config options so yea, what's the point?
frankdejonge•2h ago