3 ms·
I've been avoiding the Node.js/NPM ecosystem for this reason among others. Unfortunately more and more packages are including Node for simple scripting function
by aww_dang 5y ago
I've been avoiding the Node.js/NPM ecosystem for this reason among others. Unfortunately more and more packages are including Node for simple scripting functionality.
At this point I can no longer hold my breath and hope that the Node.js trend goes away.
- roofwellhams 5y agoIf you don't use node, what do you use? You will have the exact same problems if you want to use a library.
- aww_dang 5y agoFor js libraries, I generally prefer something that offers a prebuilt package. If I need to use NPM just to include a Javascript file on a webpage, I generally look elsewhere. Same with CSS themes. For command line tools and packages that require Node, again I generally look elsewhere. Dealing with a rest API on a command line shouldn't require so much bloat. If a tool requires Node as part of a build script, I avoid it like the plague. In other cases, I use a VM to build the JS package, but I honestly dread this workflow. Whenever a README/INSTALL contains, "Just npm our package..." or "first install node, then npm our helper utilities..." I start looking for alternatives. Maybe I'm becoming a curmudgeon and maybe my dislike of Node is irrational, but this is how I'm coping.
- dgb23 5y agoWhat would you rather download assuming you don't know if you can trust the author: The source files of a program or a distributed binary?