|
|
|
|
|
by ScriptedAlchemy
1193 days ago
|
|
This depends of how many js hooks are used and how efficient they are. Large builds with many plugins / loaders have a parallelism bottleneck with native moving data back to JS. The slower end, I’ve seen at least 5x improvement. Upper end, I’ve seen 30x. for a optimized prod build. The project is quite new & fine tuning as it matures will most likely achieve further speed gains. The big benefit is you have a webpack level api & existing ecosystem support. Many current tools offer you speed in trade for api surface. Smaller api & JS hooks, more speed. I’m not sure what the diff between them is. But a 20k cold dev build takes about 2 seconds. No incremental or lazy compilation is built in, in the initial release. Rspack offers enormous real world build gains against webpack, while preserving its ecosystem which is a very welcome balance in speed vs power. As a big user & writer of custom plugins or complex builds, I’m not necessarily looking for the absolute fastest build. If a 40 second build takes 2, and esbuild takes 1 - its a negligible difference that I’d be happy to accept for a robust api. At 50k modules, if a prod build taking ~15 seconds seems plenty fast - those represent some of the largest codebases. |
|