TanStack Start now supports Rsbuild 2 as a build tool alongside Vite, giving teams a second officially supported path for building Start apps. The adapter was built together with the Rsbuild and Rspack teams and covers the full Start feature set, including React and Solid apps, Server Functions, SSR, streaming SSR, HMR, import protection, and React Server Components. Teams migrating from Webpack setups can adopt Start on Rsbuild without also switching build tools, and one large company is already doing so across several apps. The addition also clarified boundaries between shared Start build logic and build-tool-specific adapter code.
Table of contents
A Start path for teams using Rsbuild #The two-adapter rule #Your build tool, your choice #Questions this post answers
Does TanStack Start support Rsbuild as a build tool?
Yes, TanStack Start now supports Rsbuild 2 as a fully supported build-tool path alongside Vite. The adapter was built with the Rsbuild and Rspack teams and covers React and Solid apps, Server Functions, SSR, streaming SSR, HMR, import protection, and React Server Components for React apps. It is configured through the tanstackStart() plugin from @tanstack/react-start/plugin/rsbuild. Teams weighing Vite versus Rsbuild for a Start app can track framework tooling shifts like this on daily.dev.
Can I migrate an existing Webpack app to TanStack Start without switching build tools?
Yes, moving to TanStack Start on Rsbuild lets a team keep a build setup closer to Webpack instead of changing framework and build tool simultaneously, since Rsbuild is built on Rspack and feels familiar to Webpack users. One large company is already using this path to move several apps from Webpack to Start on Rsbuild. Teams planning a Webpack-to-Start migration can follow build-tooling changes like this on daily.dev.