Are there any pros to replace Webpack with Parcel when using Angular 4+ version?
Parcel and webpack differ in how complicated applications you can build without needing a config file
Parcel
Parcel Does not require Configuration
- Parcel creates separate files for CSS, JavaScript bundle, images, etc.
- Parcel supports the following transforms without needing a Parcel
config-file:
- CSS
- SCSS
- Images
- Babel
- PostCSS
- PostHTML
- TypeScript
- ReasonML/BuckleScript ReasonReact
- Parcel autodetects what transforms are needed by checking what dependencies are installed and what config files exist.
Webpack
- webpack inlines everything in the JavaScript bundle
With webpack, the only features you get without a config file is default input and output files. If you need anything else, such as babel, SCSS, etc, you need the webpack.config.js-file
For most real projects you will still need a config file when you are using webpack 4
For MoreInfo: http://blog.jakoblind.no/parcel-webpack/
Parcel is just easier to setup by yourself (it has 0 config, like, legit) and you don't have to worry about it.
In case of angular, if you are using angular CLI, this has a bunch of configs out of the box that are going to be updated when its necessary so you don't have to worry about it.
If i'm starting a new project (without any cli of similar things) i would stick with parcel, otherwise go with the default one.