👀 Turborepo is using tsdown!
github.com/vercel/turbo...
05.03.2026 09:35
👍 21
🔁 0
💬 1
📌 0
🚀 tsdown v0.21 is released now!
github.com/rolldown/tsd...
will implement it
tsdown v0.21 is going to be a big one 🚀
What's new:
✦ Full CSS pipeline (Sass/Less/Stylus + Lightning CSS)
✦ Cross-platform executable builds via @tsdown/exe
✦ Dep options moved to deps namespace
✦ Node.js < 22.18.0 deprecated
Try the beta: npm add tsdown@beta -D
github.com/rolldown/tsd...
Followed up with a separate RFC at e18e to discuss the `inlinedDependencies` field as a broader ecosystem standard — naming, shape, and adoption — since it's relevant beyond npmx itself.
If you're interested in the standard side of things, come join the discussion there: github.com/e18e/ecosyst...
Goodbye, npmjs. com!
Wrote a RFC for @npmx.dev
The idea: surface packages that are silently bundled inside other packages' tarballs — and show their "implied downloads".
Would love feedback 👇
github.com/npmx-dev/npm...
Also applied to @e18e.dev
🎉 cac v7 just dropped — after 3.5 years!
✦ CJS build gone. Now pure ESM!
✦ No more Node.js APIs — runs in any JS runtime, even browsers
✦ Deno? It's on JSR now
✦ Repo refreshed with Vitest / tsdown / npmx
Thanks @egoist.dev for passing the torch 🙌
npmx.dev/package/cac
25.5 at least (only support CJS), require 25.7 if using ESM
🤣
Not right now, but we have plans to support it.
🚀 Coming in the next version of tsdown: built-in Node.js SEA (Single Executable Applications) support!
Now you can bundle your JS apps into a standalone executable with a single command:
tsdown --exe
ESLint v10 ships with a Node.js version requirement that necessitates `require(esm)`, yet the package remains CJS only.
Why?
It's still very much alive in Chinese indie blog circles, where it's more than SEO - it's a social ritual symbolizing friendship between bloggers and helping readers discover similar content. Think of it as the pre-social-media way of building community.
A "friend link" is basically the old-school blogroll tradition - mutual link exchanges between personal blogs/sites, usually displayed in sidebars or dedicated pages.
I didn't realize this practice has largely faded in the English-speaking web!
Finally finished building my personal website entirely with Vibe Coding!
sxzz.dev
If you’d like to exchange friend links, let me know!
I wanna say this out loud. A few months ago, I told Evan that @voidzero.dev should stop sponsoring me. I burned out, and I couldn't help Vite as before. But they decided to continue supporting me while I was down. And by doing so, they helped me get back on my feet sooner. Thank y'all ❤️
{"timestamp":"2026-01-31T18:10:40.584Z","type":"event_msg","payload":{"type":"agent_reasoning","text":"**Evaluating StackBlitz file retrieval APIs**\n\nConfirmed there is no official public API to fetch arbitrary project files server-side; only browser WebContainer APIs and project creation APIs exist. The unofficial stackblitz.zip tool uses undocumented endpoints, posing risk. Next, I'll verify these endpoints and consider safer alternatives like GitHub API access when projects originate there."}} {"timestamp":"2026-01-31T18:10:40.584Z","type":"event_msg","payload":{"type":"agent_reasoning","text":"**Preparing to cite StackBlitz docs and alternatives**\n\nI'll gather official statements from StackBlitz WebContainer and SDK docs to confirm API limitations, and also reference stackblitz.zip as an unofficial alternative. I'll review the provided MCP docs next for proper citation using web.run."}}
Haha, the API I used is the one I found in your repo
Just shipped stackblitz-mcp — my first vibe coding project!
An MCP server that lets AI read StackBlitz projects. Useful when you ask AI to debug a GitHub issue and the repro is a StackBlitz link.
stackblitz-mcp.sxzz.dev
tsdown now has an official AI skill!
Install it:
npx skills add rolldown/tsdown
Your coding agent will know how to configure builds, generate declarations, set up CI validation, bundle WASM, and more.
tsdown.dev/guide/skills
Fundamentally, npm needs a more open community ecosystem, as previous feedback channels have largely disappeared. They should actively embrace broader community input rather than relying on exclusive or restricted channels.
My guess is that it’s an optimization from the ESM transition, though I haven’t verified it yet.
Working with TypeScript is far more complex than dealing with the JS runtime itself, and the effort involved is often underestimated.
Examples: Volar.js, rolldown-plugin-dts
typesVersions will resolve it
"typesVersions": {
"*": {
"*": [
"./dist/*.d.ts",
"./*"
]
}
},
unplugin v3 has been released!
- Drops CJS build, now ESM-only, and requires Node.js >= 20.19.0
- Adds Bun support (thanks to @alistair.bsky.social)
github.com/unjs/unplugi...
After upgrading to @babel.dev v8, tsdown's startup time decreased by ~50ms.
🎉 tsdown v0.20 has now shipped, with Rolldown 1.0 RC!
