I have a project that I updated to 3.4 official release on wednesday and in the process of updating I also updated some packages. The app started loading changes very slowly, it took 2200ms to show changes in the browser while before it took max 300ms.
I have narrowed down the issue to the update of @rspack/core to v1.7.4 before it was at v1.7.2.
@nachocodoner this might be something that you might encounter in the future with more people using this version of the package.
Ill try to make a reproduction repo later today or tomorrow so that is easier to replicate the issue.
Oh, crap.
If this comes from a different @rspack/core patch version, it’s likely a regression on Rspack’s side. One option to avoid this as a workaround is to pin to a patch version where the issue doesn’t happen, report it upstream, and later move to a newer patch once it’s fixed.
Let’s see if you can reproduce it so we can report it or analyze it further. Have you added anything to your app recently?
I’ll check what you mean in their issues list and in my tests.
To confirm that I have the same problem, it takes about 2 secondes for the first paint
Does pinning @rspack/core to v1.7.1 help? (“@rspack/core”: “1.7.1” in package.json without the caret)
I’d like to confirm when this issue first appeared. If it started in a recent patch, it could be a regression in Rspack side and we can report it.
Edit: Rspack 1.7.0 also enabled many rspack.config.js options by default. If you can identify which version introduced this (an early 1.6.x?), that would help. I will run my tests later.
In my case that is how I identified the version, so pinning works in my case. Ill try creating the reproduction later today.
Indeed it does with the pin
@pmogollon did you get around making a reproduction repo? I could try taking a look.
Seems like @rspack/core 1.7.2 doesn’t have the load times regression?
I tested rspack 1.7.4 on skeleton apps and couldn’t reproduce it. I don’t see any loading delay on my side. Is this about dev experience or production?
I’d like more details on this regression to check it’s not an odd interaction with the new patch and Meteor-Rspack. If it’s a regression on the Rspack side, we can report it to them.
Sorry guys, I was a bit sick and didnt have much time. I jus tried reproducing this in a fresh project with no luck.
In the process of debugging the app to try to find the issue I was able to reduce the app bundle size to 300kb, so time well spent. But no luck on fixing this issue, the app keeps taking around 1.5s to compile.
This is most likely something specific to my stack, I tracked it back to something related to chunk names but couldnt find anything deeper than that. Ill try to reproduce this again with a similar stack in a basic app and report back.
1 Like