4 ms·

I guess I'm complaining about npm more than Angular per se. Most of our issues stem from the myriad package dependencies "in the wild" of npm itself. It's like

by IBCNU 12y ago

I guess I'm complaining about npm more than Angular per se. Most of our issues stem from the myriad package dependencies "in the wild" of npm itself. It's like tilling a field in the wind. Often one has to `npm install` >3 times to install all of your modules. I guess that's what happens when you have ten billion cooks in the kitchen.

joevandyk 12y ago
Is using npm worth it? Would it be simpler to download the dependencies yourself and put them into a vendor directory?
- IBCNU 12y ago
  You know that's a good question. I've spent about half of my work day today working out npm dependency conflicts... The Einstein quote about insanity comes to mind.
- Silhouette 12y ago
  The web development industry, and particularly the front-end side, currently seems to be obsessed with (or maybe plagued by) tools that sort of do half the job you sometimes want but feel like you have to always use anyway because everyone else is or appears to be or at least says you should on their TwitBookBlogFeed. I wanted to do exactly what you describe yesterday -- just download the latest stable version of a one-JS-file library to include on one page of a web app where its functionality is relevant. We used to do this by downloading example-1.0.8.min.js from the obvious Download link on www.example.com. As it turns out, the project from yesterday lives in a GitHub repository with a dozen files scattered across a root and four subdirectories. I honestly have no idea how to build it; it's written in a compiled-to-JS language, the build instructions are a one-liner that refer to a build tool I've heard of but never used, and there are at least half a dozen other files in the project that seem to be there only for some sort of compatibility with various other tools I've heard of but never used/don't use on this project/don't have installed on this workstation. I find myself reminded almost daily of this now-infamous XKCD: http://xkcd.com/927/ http://xkcd.com/927/ This is not progress. :-(

by IBCNU 12y ago

joevandyk 12y ago

Is using npm worth it? Would it be simpler to download the dependencies yourself and put them into a vendor directory?

IBCNU 12y ago
You know that's a good question. I've spent about half of my work day today working out npm dependency conflicts... The Einstein quote about insanity comes to mind.
Silhouette 12y ago
The web development industry, and particularly the front-end side, currently seems to be obsessed with (or maybe plagued by) tools that sort of do half the job you sometimes want but feel like you have to always use anyway because everyone else is or appears to be or at least says you should on their TwitBookBlogFeed. I wanted to do exactly what you describe yesterday -- just download the latest stable version of a one-JS-file library to include on one page of a web app where its functionality is relevant. We used to do this by downloading example-1.0.8.min.js from the obvious Download link on www.example.com. As it turns out, the project from yesterday lives in a GitHub repository with a dozen files scattered across a root and four subdirectories. I honestly have no idea how to build it; it's written in a compiled-to-JS language, the build instructions are a one-liner that refer to a build tool I've heard of but never used, and there are at least half a dozen other files in the project that seem to be there only for some sort of compatibility with various other tools I've heard of but never used/don't use on this project/don't have installed on this workstation. I find myself reminded almost daily of this now-infamous XKCD: http://xkcd.com/927/ http://xkcd.com/927/ This is not progress. :-(