2 ms·
"People pull hundreds of dependencies" only because Babel decided to split their package which used to be only one into hundreds of dependencies. A vanilla ins
by whstl 4y ago
"People pull hundreds of dependencies" only because Babel decided to split their package which used to be only one into hundreds of dependencies.
A vanilla installation of create-react-app pulls 133 babel-owned packages, last I counted. If you pull all the available packages from @babel, it's 153. They all live in the same Github repo, since who would want to manage that many packages. The second biggest offender in the ecosystem has a whole order of magnitude less packages than that.
Babel is the #1 cause for the JS ecosystem being the "royal shitshow" you and other people claim it to be.
- SillyUsername 4y ago^ This. I'm a BE dev, but occasionally do FE maintenance. I wrote a few pages of Typescript with a young FE developer and it pulled in a ton of Babel dependencies on build which was literally 90% of the packed archive. I still have no idea what they were needed for, neither it seems did the FE dev.