Hacker News new | past | comments | ask | show | jobs | submit login

Version 5 and this tool still has absolutely awful UX.

I have no problem configuring Webpack, but it's ridiculous that:

- it needs two plugins to generate CSS files [1], when the homepage lists it as one of the supported outputs in front and center; [2]

- it needs a plugin have a non-trash output log. [3]

Parcel was supposed to fix the situation, and in many cases its UX is an order of magnitude better, but in exchange it brings a slew of unfixed bugs in the most simple projects that lightly sway from the base usage.

Maybe in 2030 the JS community will have figured something out.

1: https://webpack.js.org/guides/asset-management/#loading-css

2: https://webpack.js.org

3: https://github.com/GoogleChromeLabs/size-plugin




IMO it's the beauty of webpack that they are dogfooding their own APIs and even the basics are implemented as plugins & loaders.

Maybe out there is a better way to design a bundler api. But up until now I only see a flood of one-click bundlers that cover the happy path.


Exactly my problem with it, it doesn’t just work with CSS, which is a part of the bigger problem seen above: equating Frontend with JS.




Consider applying for YC's Summer 2025 batch! Applications are open till May 13

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: