Sep 25, 2020
I would like to comment on the https://css-tricks.com/why-parcel-has-become-my-go-to-bundler-for-development/
"Parcel does not need any configuration" is not true. And I am not talking about any advanced stuff but pretty much things that 90% of developers come across with.
Here is why:
Want to copy static assets (such as robots.txt, favicon.ico) ? - You mush install a plugin "parcel-plugin-static-files-copy" and configure it .
Want to keep ids in inline svg? - You must create a ".htmlnanorc" file and configure it
Want to share your style.css file between pages? - you must create linker js files, otherwise, it will not work, https://github.com/parcel-bundler/parcel/issues/2340
Want to use inline style for whatever reason? - you can't, the bundler with not work correctly.
Some of the bugs have been reported ages ago and are still not fixed. So I would be very careful using this bundler in production yet.
PLEASE BE WARNED!!!
I would like to hear your advice how does it compare and what I need in webpack in order for the above to work.