Node.js 20+ and TypeScript 6.0 now let you write subpath imports with a bare "#/*" prefix.
Rspack supports it too — so you can map "#/*" directly to ./dist/* (or ./src/*)
Clean, familiar, and one step closer to the "@/" bundler experience 🦀
#Rspack #WebDev #JavaScript
That’s a fair point, I agree there are tradeoffs here.
Vite and Next.js have been doing this for years. In our case, we started exploring it around ~4 years ago in our internal frameworks, it helps reduce the dependency management burden for our business teams.
Thanks for the context. Just to clarify, I don’t always bundle dependencies. For develop tools like Rspack or Rsbuild, we prioritize fast CLI startup and stability, so that’s the trade-off we chose.
In my experience, bundling deps often reduces the install size.
I understand the need to control versions in some cases. But most users aren’t able to manage hundreds of transitive deps effectively. Having frameworks or build tools bundle and pin them is usually a simpler and more reliable default.
How we achieved this:
- moved non-essential deps to optional peer deps
- replaced heavy deps with lighter alternatives
- bundled some deps into the output
- leveraged Node 20+ native APIs (e.g. styleText over picocolors)
Rspack / Rsbuild 2.0 stable is coming next week!
One key improvement: we've trimmed npm deps across core packages to the bare minimum. This lowers supply chain risk and speeds up installs.
Setting up Rstest just got easier.
Rstest docs now include a dedicated guide for coding agents to do it for you:
Rslint is part of Rstack. It currently uses tsgo to support TypeScript, with this part primarily implemented in Go. We also plan to introduce Rust to implement additional capabilities.
Just tried "rslint --type-check":
2s for type-aware linting + type checking on the Rsbuild monorepo 🚀
Rsbuild reached 1M weekly downloads. Thank you all ❤️
Lots of ecosystem and community updates, too:
⚡ @vite.dev 8
▲ @nextjs.org 16.2
📝 @eslint.org 10
🅰️ @angular.dev 21
🦀 CLI init support for Rsbuild
⚡️ @preactjs.com support for Vitest addon
🤘 Community @vike.dev integration
🚀 Community @astro.build framework (experimental)
Here's what we reached for 👇
→ Lit and web components for all interactivity
→ Custom server components for static templating
→ Rspack instead of Webpack
→ Declarative Shadow DOM for instant rendering
→ Baseline to decide which web APIs we can ship with confidence
As part of this effort, since the connect package is no longer actively maintained, I forked and modernized it.
Fewer dependencies, rewritten in TypeScript, and now native ESM.
github.com/rstackjs/con...
Update: reduced @rspack/dev-server deps from 193 → 8, install size from 14.9 MB → 4.1 MB.
npm supply chain attacks keep happening and keeping deps minimal makes me feel safer.
🆕 Introducing rspress-custom-theme skill
🎨 One prompt → a fully themed docs site + custom homepage
⚡ Generated in seconds, ready to use
Try it out👇
```bash
npx skills add rstackjs/agent-skills --skill rspress-custom-theme
```
Learn more 🦀
🔗 github.com/rstackjs/age...
🔗 rspress.rs/guide/start/ai
Some recent Rspack benchmark trends.
Rspack 2.0 work is helping improve performance steadily⚡️
We’re getting close ⏳
Rspack 2.0 and Rsbuild 2.0 are landing next month.
Beta is already out. give it a try and share your early feedback with us.
For the second issue, import defer might help in the future.
Runtime support is still limited today, but Rspack already supports bundling it behind experiments.deferImport . So one possible direction for us could be to bundle the config with Rspack at startup to reduce the eager cost from imports.
3. for task management and build cache, projects like Turborepo and Nx already do a great job, so we’d rather build on top of that ecosystem than reinvent it
1. it makes dependency/version management more coupled, especially around major upgrades in underlying tools
2. it can lead to a single large config file, and if that file imports several third-party packages, it may slow down command startup
Rstack could offer a unified toolchain experience similar to Vite Plus as well, and huge respect to the Vite Plus team for exploring that direction.
We haven’t pursued that path for now, mainly because we worry about a few tradeoffs:
New doc added: Rspack + AI 🤖: rspack.rs/guide/start/ai
Learn how to use coding agents to set up and work with Rspack projects more efficiently.
Still curious why memfs v4 introduced so many new dependencies compared to v3.
Working on modernizing Rspack dev server.
No longer tied to webpack-dev-server compatibility. Dependencies are updated and unnecessary ones removed.
Early progress:
📉 Direct deps: 28 → 9
📉 Transitive deps: 193 → 76
📉 Install size: 14.9MB -> 9.9MB
Rspack just hit 4M weekly downloads.
Vibe coding is helping dev tools grow faster. 🚀
0→1M: 750d
1→2M: 160d
2→3M: 140d
3→4M: 40d
Introducing Rstack Agent Skills:
- rspack-best-practices
- rspack-v2-upgrade
- rspack-debugging
- rsbuild-best-practices
- rspress-v2-upgrade
- rsdoctor-analysis
- migrate-to-rsbuild
- migrate-to-rstest
- more...
github.com/rstackjs/age...
Great to see Tailwind CSS shipping an official @tailwindcss/webpack package 👏
It’s implemented as a webpack loader, which means it works in Rspack and Turbopack as well.
Big shoutout to @timneutkens.bsky.social for making this happen 🙌
