Re:Yarn Plug'n'Play: Getting rid of node_modules
by codingdave on Thursday September 13, 2018 @08:36AM
(#17978077)
Bringing packages into your work is your own choice. You should always be doing an evaluation of the benefit given by a package vs. the bloat it brings to your project. For many packages, it is worth it. But if you are in the habit of installing a package just to avoid writing a widget in your UI or writing some helper functions, then... yes, your projects will amass dependencies quickly.
[ Parent
| on HN ]
Re:Yarn Plug'n'Play: Getting rid of node_modules
by jannes on Thursday September 13, 2018 @08:39AM
(#17978089)
My main complaint is probably about webpack and its dependencies. Unfortunately, it seems to be the accepted standard bundler. The benefits of hot module replacement are too nice to forego easily.
Re:Yarn Plug'n'Play: Getting rid of node_modules
by mschuetz on Thursday September 13, 2018 @10:24AM
(#17978817)
The ridiculous amount of dependencies in webpack is one of the major reasons I went for rollup. I refuse to install anything that depends on is-odd.
Re:Yarn Plug'n'Play: Getting rid of node_modules
by mifreewil on Saturday September 15, 2018 @07:29PM
(#17996542)
Not sure that webpack still depends on `is-odd` (at least not directly). Note that `is-odd` depends on `is-number` facepalm. Some people in this world seem to think their purpose is to create as many JS modules as possible.