Originally from Last 3.4-beta.14 Release, Faster Builds, Smaller Bundles and Modern Setups with the Rspack integration ⚡ - #155 by schlaegerz
Hey! Just in case there is someone else already trying to do this, I’m trying to add the React Router framework to a basic template…
Based on what I’ve searched, for RSpack, I would need to use/add GitHub - rspack-contrib/rsbuild-plugin-react-router: A Rsbuild plugin that provides seamless integration with React Router and have this configuration and it would kinda work:
import { defineConfig } from '@rsbuild/core';
import { pluginReactRouter } from 'rsbuild-plugin-react-router';
import { pluginReact } from '@rsbuild/plugin-react';
export default defineConfig(() => {
return {
plugins: [
pluginReactRouter({
// Optional: Enable custom server mode
customServer: false,
// Optional: Specify server output format
serverOutput: "commonjs",
//Optional: enable experimental support for module federation
federation: false
}),
pluginReact()
],
};
});
I did a small search on the forum, and was never mentioned @rsbuild, I assume we(meteor) do the part of the rsbuild, how could this config be in my meteor case?
atm my config is:
And my repo is here: GitHub - Grubba27/meteor-with-rspack-and-react-router: Meteor with RSPack + React Router
And the error I’m getting is this one:
As a side note, just check the vibe: how people feel about having our React template come with a router configured (similar to what we have for Vue)?
- React Router
- Tanstack Router
- Other(please reply)
- Yes
- No
- YES and more(tailwing, for example) – please reply with your ideas
