Skip to content

RSPFx

Ship SharePoint web parts without the legacy toolchain

SPFx development shouldn't be frustrating. RSPFx dev server runs in seconds with modern tooling (Vite, Rsbuild, Rspack) — not minutes waiting on Heft and webpack.

Get started
RSPFx — build SharePoint web parts with Vite
1.20 – 1.24 SPFx targets0 deps coreVite · Rsbuild · Rspack1 line spfxVersion switch

Start in seconds

sh
npm create vite@latest my-app -- --template react-ts
cd my-app
sh
npm i -D @mbsks/rspfx-plugin @mbsks/rspfx-cli
# add rspfxVite() to vite.config.ts + manifests, then
rspfx dev          # http://localhost:4321 — no tenant needed
rspfx package      # → sharepoint/solution/my-app.sppkg
# any starter works: better-t-stack, TanStack Router, etc. — just add the plugin
# shortcut: rspfx new my-app

Switch SPFx versions with one line — spfxVersion: '1.20''1.24' — then update your package. See Compatibility and Upgrading SPFx.

How it compares

Official toolchain (Heft / gulp)RSPFx
Bundlerwebpack onlyVite (default), Rsbuild, Rspack
FrameworksReact, vanillaReact, Vue, Svelte, Solid, Preact + custom presets
SPFx switchnew project / pin updatesone line spfxVersion + package manager update
Dev servergulp serve :4321rspfx dev :4321 — tenant optional
Package managernpm / yarn / pnpmnpm · pnpm · yarn · bun · deno
Config requiredrig + gulpfile requiredzero-config from config/config.json + manifests
Before first devRun rspfx doctor — it checks Node version, cert trust, port conflicts and missing manifests in one pass.

Released under the MIT License.