Rspack plugin feedback #77800
Replies: 33 comments 75 replies
-
|
let’s go 🚀 |
Beta Was this translation helpful? Give feedback.
-
Environment
Reproduction procedure
ErrorRspack plugin The error stacktrace |
Beta Was this translation helpful? Give feedback.
-
|
@cooke00123 I think you need to install @next/plugin-rspack as canary as well. |
Beta Was this translation helpful? Give feedback.
-
|
I was able to avoid the error, but the third party didn't support the canary version and I couldn't figure out the effect. |
Beta Was this translation helpful? Give feedback.
-
|
i got it working well but in dev it disconnects from hmr many times over, I don't have logs at hand though, had to revert |
Beta Was this translation helpful? Give feedback.
-
|
Hi, currently, my project is using Next.js v13 with Webpack. Is there any workaround to migrate the bundler to Rspack? Alternatively, do you have any suggestions for a different bundler that works well with Next.js v13? My application is getting larger and feels slower, so I’d appreciate any advice. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately no, you'll have to upgrade. Can I ask what's blocking you from doing so? |
Beta Was this translation helpful? Give feedback.
-
We use version 14.2.3 of next.js in the production environment, because version 15+ requires React to be upgraded to 19+, which is a major compatibility challenge for our project. We look forward to your compatibility with version 13+ |
Beta Was this translation helpful? Give feedback.
-
|
When using a monorepo, packages with 15.3.0-canary.36, did something and it's not working anymore in our repo. Some benchmarks 
Rspack doesn’t seem to have caching enabled right now. Running it multiple times doesn’t reduce compile times like the version with turbo does (using the experimental flag), or even the version without turbo. I welcome the idea of having another builder. Turbo looks great on paper, and I haven’t found that many errors lately, but it still breaks often for other developers. Offering Rspack as an option will make many devs happier. |
Beta Was this translation helpful? Give feedback.
-
|
Since >15.3.0-canary.36 I also get errors trying to use custom loaders with rspack. With 15.3.0-canary.36 and below it works fine. |
Beta Was this translation helpful? Give feedback.
-
|
@dlehmhus it's working again with 15.3.0-canary.41 |
Beta Was this translation helpful? Give feedback.
-
|
In my case I was the problem - I didn't realise that |
Beta Was this translation helpful? Give feedback.
-
|
I've been testing next-rspack with our repo, and one of the issues that comes up is to do with the @sentry/nextjs plugin. This is responsible for uploading sourcemaps to sentry during the build. I double checked that the issue was not just because we are using an older major (7) vs the latest (9), and I see different errors for both. On the latest, 9.11.0, I get this error On 7.114.0, I get this error I have confirmed that removing the withRSPack step removes these errors. Cheers, |
Beta Was this translation helpful? Give feedback.
-
|
Also next-pwa at 5.6.0 gives the same issue |
Beta Was this translation helpful? Give feedback.
-
|
thanks for feedback and we will be investigating how to support sentry and pwa |
Beta Was this translation helpful? Give feedback.
-
|
Hey @hardfist, is this in roadmap / priority of rspack team to work upon? |
Beta Was this translation helpful? Give feedback.
-
|
For the
export async function register() {
const { init } = await import('@hyperdx/node-opentelemetry');
}
{
"dependencies": {
"@hyperdx/node-opentelemetry": "0.8.2"
}
} |
Beta Was this translation helpful? Give feedback.
-
|
In dev mode, when loading a page, I see a warning “Failed to lookup module by ID” for every server action file that the page depends on: (Each of these referenced files has |
Beta Was this translation helpful? Give feedback.
-
|
@hardfist I noticed a similar error message, but in combination with HMR. Steps to reproduce:Clone repo: Inside the repo:
Next Info |
Beta Was this translation helpful? Give feedback.
-
|
same issue, Failed to lookup module by ID |
Beta Was this translation helpful? Give feedback.
-
|
Maybe related: When I enable persitent cache in rspack const config: NextConfig = {
webpack: (config) => {
config.experiments ??= {};
config.cache = true;
config.experiments.cache = {
type: 'persistent',
storage: {
type: 'filesystem',
directory: '.next/cache/rspack',
},
};
return config;
},
};and start the dev server, load a page, stop and restart the dev server again, I get the same error messages: |
Beta Was this translation helpful? Give feedback.
-
|
@dlehmhus what's the result when you disable persistent cache? |
Beta Was this translation helpful? Give feedback.
-
|
@hardfist when I don't explicitly set the cache, just use the next defaults, I can restart the server and the initial render works fine. The issues mentioned above when updating files still persist. I need to try what happens when I disable the cache. |
Beta Was this translation helpful? Give feedback.
-
|
Hey, I was trying out Rspack with PayloadCMS and when trying to build this error happens: |
Beta Was this translation helpful? Give feedback.
-
|
For the
export async function register() {
const { init } = await import('@hyperdx/node-opentelemetry');
}
{
"dependencies": {
"@hyperdx/node-opentelemetry": "0.8.2"
}
} |
Beta Was this translation helpful? Give feedback.
-
|
rs: next: hello, Thank you for your improvements, but I only see a 1 second difference when I test it. rspack : next: |
Beta Was this translation helpful? Give feedback.
-
|
do you use app router？ |
Beta Was this translation helpful? Give feedback.
-
|
Rspack only works with Next >=15.3.0 |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Tried it and we get a lot of issues like this
|
Beta Was this translation helpful? Give feedback.
-
|
is |
Beta Was this translation helpful? Give feedback.
-
|
It's an absolute path in typescript |
Beta Was this translation helpful? Give feedback.
-
|
that's weird, may needs more info to investigate |
Beta Was this translation helpful? Give feedback.
-
|
I am using pages router, output export, and NO custom webpack config My package json has next info |
Beta Was this translation helpful? Give feedback.
-
|
yes, lightningcss use [email protected] to parse query which is outdated than browserslist(javascript version) |
Beta Was this translation helpful? Give feedback.
-
it's hard to do that, the query is complex and we can't easily fallback to an older version |
Beta Was this translation helpful? Give feedback.
-
|
it's actually a tricky issue, since browserslist and browserslist-rs is not updated together, so it may generate different result, I will try to upgrade browserslist-rs to latest version, but I suggest use more explicit query other than things like |
Beta Was this translation helpful? Give feedback.
-
same error now with android version 137 |
Beta Was this translation helpful? Give feedback.
-
|
same error now with android version 133 |
Beta Was this translation helpful? Give feedback.
-
|
I'm getting this error with mapbox + |
Beta Was this translation helpful? Give feedback.
-
|
Is it a warning or error ? doesn't webpack throw same error(warning)? |
Beta Was this translation helpful? Give feedback.
-
|
it failed after that and doesn't happen in webpack. |
Beta Was this translation helpful? Give feedback.
-
|
sorry I can't reproduce your error in minimal repo, can you reproduce this bug with minimal repo using this https://github.com/vercel/next.js/tree/canary/examples/with-rspack |
Beta Was this translation helpful? Give feedback.
-
|
Super excited by this. In our repo, we already use Rsbuild for non-Next.js applications. Is there a simple way to reuse its config without having to build a second config for Rspack? One middle-ground could be to use e.g. DEBUG mode to spit out the generated Rspack config. My concern is around possible breaking changes in minor versions as this wouldn't be a documented thing |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure whether I understand your problem, the next-rspack integration is more than simple rspack config, so it seems hard to split next.js rspack configuration |
Beta Was this translation helpful? Give feedback.
-
|
Ah sorry, so this integration wouldn't read an |
Beta Was this translation helpful? Give feedback.
-
|
no, it's nearly same as webpack version, so if your |
Beta Was this translation helpful? Give feedback.
-
|
Got it, thanks 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Is Yarn PNP currently not supported?
|
Beta Was this translation helpful? Give feedback.
-
|
Rspack supports yarn pnp but not sure whether next-rspack works well in yarn pnp now |
Beta Was this translation helpful? Give feedback.
-
|
Following the instructions at https://rspack.dev/guide/tech/next
Manually adding @rspack/core to the monorepo root gives me:
|
Beta Was this translation helpful? Give feedback.
-
|
I just ended up at this while attempting to upgrade from 14 -> 15 Also using PnP. The alias is resolved as Had to patch Next against #71759 and add both @rspack/core and next-rspack to Next.js as dependencies (would otherwise not resolve properly) to get to a point where the dev server actually starts, but fails to resolve modules on the first request. |
Beta Was this translation helpful? Give feedback.
-
|
Generating a manifest file with manifest.ts throws the following error: Import trace for requested module:
next-metadata-route-loader?filePath=%2FUsers%2Fusername%2FCode%2Facme%2Fproject-name%2Fapps%2Fapp-name%2Fsrc%2Fapp%2Fmanifest.ts&isDynamicRouteExtension=1!?__next_metadata_route__
⨯ next-metadata-route-loader?filePath=%2FUsers%2Fusername%2FCode%2Facme%2Fproject-name%2Fapps%2Fapp-name%2Fsrc%2Fapp%2Fmanifest.ts&isDynamicRouteExtension=1!?__next_metadata_route__
× Module build failed:
╰─▶ × TypeError: context.loadModule is not a function
│ at mod (/Users/username/Code/acme/project-name/node_modules/.pnpm/next@15.3.1-canary.11_@opentelemetry+api@1.9.0_@playwright+test@1.50.1_babel-plugin-react-com_dcec2llys6a7epps6btzp2zqra/node_modules/next/dist/build/webpack/loaders/utils.js:76:17)
│ at new Promise (<anonymous>)
│ at getLoaderModuleNamedExports (/Users/username/Code/acme/project-name/node_modules/.pnpm/next@15.3.1-canary.11_@opentelemetry+api@1.9.0_@playwright+test@1.50.1_babel-plugin-react-com_dcec2llys6a7epps6btzp2zqra/node_modules/next/dist/build/webpack/loaders/utils.js:75:23)
│ at createReExportsCode (/Users/username/Code/acme/project-name/node_modules/.pnpm/next@15.3.1-canary.11_@opentelemetry+api@1.9.0_@playwright+test@1.50.1_babel-plugin-react-com_dcec2llys6a7epps6btzp2zqra/node_modules/next/dist/build/webpack/loaders/next-metadata-route-loader.js:40:70)
│ at getDynamicTextRouteCode (/Users/username/Code/acme/project-name/node_modules/.pnpm/next@15.3.1-canary.11_@opentelemetry+api@1.9.0_@playwright+test@1.50.1_babel-plugin-react-com_dcec2llys6a7epps6btzp2zqra/node_modules/next/dist/build/webpack/loaders/next-metadata-route-loader.js:122:9)
│ at Object.nextMetadataRouterLoader (/Users/username/Code/acme/project-name/node_modules/.pnpm/next@15.3.1-canary.11_@opentelemetry+api@1.9.0_@playwright+test@1.50.1_babel-plugin-react-com_dcec2llys6a7epps6btzp2zqra/node_modules/next/dist/build/webpack/loaders/next-metadata-route-loader.js:256:26)
│ at LOADER_EXECUTION (/Users/username/Code/acme/project-name/node_modules/.pnpm/@rspack+core@1.3.4/node_modules/@rspack/core/dist/index.js:5481:18)
│ at runSyncOrAsync2 (/Users/username/Code/acme/project-name/node_modules/.pnpm/@rspack+core@1.3.4/node_modules/@rspack/core/dist/index.js:5482:6)
│ at node:internal/util:433:21
│ at new Promise (<anonymous>)
│ at runSyncOrAsync2 (node:internal/util:419:12)
│ at isomorphoicRun (/Users/username/Code/acme/project-name/node_modules/.pnpm/@rspack+core@1.3.4/node_modules/@rspack/core/dist/index.js:6270:23)
│ at runLoaders (/Users/username/Code/acme/project-name/node_modules/.pnpm/@rspack+core@1.3.4/node_modules/@rspack/core/dist/index.js:6326:56)
Import trace for requested module:
next-metadata-route-loader?filePath=%2FUsers%2Fusername%2FCode%2Facme%2Fproject-name%2Fapps%2Fapp-name%2Fsrc%2Fapp%2Fmanifest.ts&isDynamicRouteExtension=1!?__next_metadata_route__
GET /manifest.webmanifest 500 in 4826ms |
Beta Was this translation helpful? Give feedback.
-
|
@dlehmhus It is a known issue with Rspack, and we are currently working on resolving it. |
Beta Was this translation helpful? Give feedback.
-
|
Track this issue through web-infra-dev/rspack#7723 |
Beta Was this translation helpful? Give feedback.
-
|
how do I enable experimental features? mainly I want to enable persistent caching. |
Beta Was this translation helpful? Give feedback.
-
|
@heyitsarpit Thank you for using Rspack, but we are not ready for persistent caching yet. |
Beta Was this translation helpful? Give feedback.
-
|
Module not found: Can't resolve @ — has anyone found a solution? None of the previous comments have worked. |
Beta Was this translation helpful? Give feedback.
-
|
@jheng-jie I will investigate this issue. |
Beta Was this translation helpful? Give feedback.
-
|
I eventually replaced all alias paths with the package name mechanism provided by Yarn workspaces, using prefixes like The project uses the Page Router with 8 languages in SSG mode, totaling 550 pages. In development mode, the time from initial startup to accessing some pages. use next-rspack use webpack |
Beta Was this translation helpful? Give feedback.
-
|
@jheng-jie I couldn't reproduce it, please provide a minimum reproduction, |
Beta Was this translation helpful? Give feedback.
-
|
@SyMind Hello, this is the minimal repository I created. The instructions are all in the README. If it's convenient, please also take a look at the PWA issue. |
Beta Was this translation helpful? Give feedback.
-
|
@jheng-jie We trace the issue in web-infra-dev/rspack#10487 |
Beta Was this translation helpful? Give feedback.
-
|
Hi there! Does anyone had this error before?
|
Beta Was this translation helpful? Give feedback.
-
|
@emulienfou You should use the next-rspack latest canary too, like [email protected] |
Beta Was this translation helpful? Give feedback.
-
|
That was the issue, thanks @SyMind |
Beta Was this translation helpful? Give feedback.
-
|
What is the min Next.js version that supports rspack? |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
I tried to use this plugin and the build compiles with no issues but the resulting global bundle is way bigger than in the default webpack-based build (I see modules there that definitely shouldn't be in the global bundle). Using |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! I suspect the issue was caused by the packages in our pnpm workspace rather than a third-party library. I'll try to make a minimal example if the patch didn't work out. |
Beta Was this translation helpful? Give feedback.
-
|
@SyMind |
Beta Was this translation helpful? Give feedback.
-
|
To make matters more confusing: This problem is not present when building locally (on windows), but it happens in github actions in the CI. So OS related? |
Beta Was this translation helpful? Give feedback.
-
|
I just checked on Windows and can confirm - Rspack produces even smaller shared chunk than Webpack. |
Beta Was this translation helpful? Give feedback.
-
|
looks like this regex next.js/packages/next/src/build/webpack-config.ts Line 1209 in d608590 does not match on Windows because of missing [\\]but, in the default config most modules don't match either because of module size check: next.js/packages/next/src/build/webpack-config.ts Line 1147 in d608590 on Linux (with Rspack) however, first regex matches and there's no size checking and that's where the difference comes from. |
Beta Was this translation helpful? Give feedback.
-
|
is module federation intended to work with next-rspack? would be amazing to see. |
Beta Was this translation helpful? Give feedback.
-
|
Updated to Works properly on Next 16 beta |
Beta Was this translation helpful? Give feedback.
-
Here is the fix i guess #85221 |
Beta Was this translation helpful? Give feedback.
-
|
@r34son yes |
Beta Was this translation helpful? Give feedback.
-
16.0.1, still: |
Beta Was this translation helpful? Give feedback.
-
|
Tried rspack with next > [email protected] dev /home/torten/tpa-news
> next dev
Trace: Cannot call withRspack and pass the --webpack flag.
at console.trace (/home/torten/tpa-news/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/node-environment-extensions/console-dev.js:111:32)
at withRspack (/home/torten/tpa-news/node_modules/.pnpm/[email protected]_@[email protected]/node_modules/next-rspack/index.js:13:13)
at Object.<anonymous> (/home/torten/tpa-news/next.config.compiled.js:42:40)
at Module._compile (node:internal/modules/cjs/loader:1730:14)
at requireFromString (/home/torten/tpa-news/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/build/next-config-ts/require-hook.js:81:7)
at transpileConfig (/home/torten/tpa-news/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/build/next-config-ts/transpile-config.js:98:51)
at async loadConfig (/home/torten/tpa-news/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/server/config.js:1013:36)
at async Module.nextDev (/home/torten/tpa-news/node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/next/dist/cli/next-dev.js:190:14)``` |
Beta Was this translation helpful? Give feedback.
-
|
This seems to be a version compatibility issue. At least with version 15.5.56, this was working correctly. |
Beta Was this translation helpful? Give feedback.
-
|
@next-rspack/core": "1.0.0" didn't work, so I tried the beta version, but I'm getting the following error: Update: The same error occurred with version 1.0.0 (i.e., the latest
|
Beta Was this translation helpful? Give feedback.
-
|
This particular error was fixed in |
Beta Was this translation helpful? Give feedback.
-
|
A few issues we spotted while migrating a rather large application:
Just removing the hardcoded
|
Beta Was this translation helpful? Give feedback.
-
|
Just for context: |
Beta Was this translation helpful? Give feedback.
-
|
I will work on it. |
Beta Was this translation helpful? Give feedback.
-
|
Issue with 16.0.3 I know the logs say to create an issue in another repo, I am creating it here in case others face the same issue. full command lognext infoI can provide more details if necessary. |
Beta Was this translation helpful? Give feedback.
-
|
can you give me a reproducibility repository. |
Beta Was this translation helpful? Give feedback.
-
|
Hey everyone! 👋 I've been trying out next-rspack in my Next.js projects and I'm really excited about the build performance benefits! The speed improvements are fantastic, and I'm grateful for all the work the teams are putting into this. I'm currently exploring micro-frontend architectures and was wondering about Module Federation support. I know next-rspack is still experimental, and I'm curious if anyone has insights on: What the future might look like for Rspack feature support in Next.js - particularly around Module Federation? Are there any workarounds or approaches that folks have found helpful for micro-frontends with Next.js in the meantime? How can we best support the development and testing of these experimental features? I completely understand that these integrations take time and careful planning, especially with Next.js's awesome SSR capabilities and routing system. Just excited to learn more about what might be coming down the road! 🚀 Thanks so much for any thoughts or experiences you can share! |
Beta Was this translation helpful? Give feedback.
-
|
In the next16.05 and next-rspack16.05 environment, the UI switches faster than compile is displayed, resulting in a flickering FOUC in the UI. |
Beta Was this translation helpful? Give feedback.
-
|
Updated from Next 16.0.2 to 16.0.6, now CSS import ordering get's messed up every time Fast Refresh rerenders the page. A hard refresh on the browser fixes it, but as soon as I make a code change that triggers Fast Refresh, the CSS is broken again. Initially the css imported in the root layout has the highest precedence. But after a Fast Refresh, css modules are moved up to the top. In my root css I define a |
Beta Was this translation helpful? Give feedback.
-
|
After bisecting canary versions I was able to pinpoint that this issue was first introduced in 16.0.2-canary-10 |
Beta Was this translation helpful? Give feedback.
-
|
@SyMind tagging you as it seems directly related to the changes to CssChunkingPlugin |
Beta Was this translation helpful? Give feedback.
-
|
ok |
Beta Was this translation helpful? Give feedback.
-
|
Next 16 + rspack breaks Per maintainer's request:
|
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Please use this thread for posting feedback when using the
next-rspackplugin package.When posting, provide the following:
next infoThe Rspack plugin is currently experimental, and is a partner effort with the Rspack team.
Beta Was this translation helpful? Give feedback.
All reactions