You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
core-js-builder uses webpack as its dependency. Because webpack has many dependencies, introducing core-js-builder in a project will indirectly introduce many dependencies of webpack, which increases project management costs.
Can we use rollup to replace the webpack in core-js-builder? Thank you so much.
The text was updated successfully, but these errors were encountered:
Currently, core-js-builder uses old Webpack for legacy and compatibility reasons - in core-js@3 we can't replace it with something else.
In @4 version, I wanted to replace Webpack with esbuild. It could be helpful in some other cases like service for good performance reasons. However, some related esbuild issues like this are still not fixed.
Some time ago I considered rollup and rejected this option, I already don't remember the specific reason.
You might want to wait a bit and consider using Rolldown, a Rust port of Rollup developed by Evan You, the rspack team, and the Rollup author (https://www.javascriptjam.com/november-22-2023/).
core-js-builder uses webpack as its dependency. Because webpack has many dependencies, introducing core-js-builder in a project will indirectly introduce many dependencies of webpack, which increases project management costs.
Can we use rollup to replace the webpack in core-js-builder? Thank you so much.
The text was updated successfully, but these errors were encountered: