5 ms·
npm is worse IMO. First it forces the node_module in your repository, which mean you have to configure tons of tools to ignore it or you'll have a bad time. T
by sametmax 7y ago
npm is worse IMO.
First it forces the node_module in your repository, which mean you have to configure tons of tools to ignore it or you'll have a bad time.
Then there is no way to have comfortable local command, so plenty of time you gotta have sudo -g. Recent npm version now have a tool for that but the experience is meh.
Plus there is no builtin tool to manage several versions of node, so you gotta add nvm on top of that.
And then if you work on the front end, you can't even use whatever you npm installed stuff, you gotta setup the entire webpack shenaigan, making it literally the hardest stuff to setup. It's so complicated we rely on black box such as create-react-app to do the job for us.
- jononor 7y ago> Then there is no way to have comfortable local command, so plenty of time you gotta have sudo -g. Recent npm version now have a tool for that but the experience is meh. export PATH=$PATH:./node_modules/.bin/ or put the command into `scripts` of package.json, and use `npm run-script foo`. Have never used npm -g, and never will. Global packages are owned by the system package manager.
- sametmax 7y agoLocal commands doesn't mean you have a project. It can be a general utility.