Lol. Many times you need 1 function. The “modern” approach is to use a library because it means someone else is maintaining and testing (ha!) the code. So instead of making your own complete with your own bugs, you install a library that does this thing.
But it generally doesn’t just do one thing. It probably does 30 things. And that library was built on the same principle. So it needs 6 or 7 or 20 libraries itself to do its 30 things. And those need 20 more libraries to do their things. Etc.
Npm is a package manager. It installs the dependencies you need, as well as recursively installing the dependencies they need, etc. On a new project this can take a very very long time. And the force because of course none of the packages are maintained and they all have dependency violations between them but you just ignore the warnings and soldier on. Including a bunch of code that may or may not explode at any time because it’s easier.
npm install everything --force
Someone please explain this for those of us who make under 100k
Lol. Many times you need 1 function. The “modern” approach is to use a library because it means someone else is maintaining and testing (ha!) the code. So instead of making your own complete with your own bugs, you install a library that does this thing.
But it generally doesn’t just do one thing. It probably does 30 things. And that library was built on the same principle. So it needs 6 or 7 or 20 libraries itself to do its 30 things. And those need 20 more libraries to do their things. Etc.
Npm is a package manager. It installs the dependencies you need, as well as recursively installing the dependencies they need, etc. On a new project this can take a very very long time. And the force because of course none of the packages are maintained and they all have dependency violations between them but you just ignore the warnings and soldier on. Including a bunch of code that may or may not explode at any time because it’s easier.