It is, until it isn’t. I’ve seen devs delete or abandon their projects because of too mush abuse. Nobody likes being yelled at. (Unless that’s your kink. I won’t judge.)
It didn’t break his computer. In trying to fix it, he deleted his node_modules directory, and now he’s complaining that he has to run npm install and wait for it to finish.
So to be clear, it was his own action that caused him to have to reinstall everything.
I love it. It’s my go to if I’m bored sitting on the couch. They’ve got a lot of great shows like Game Changer, Make Some Noise, and this new one called Very Important People. If you’re into D&D, there’s Dimension 20. I’m not a big fan of it, but it’s one of, if not the, most popular shows on there.
Yeah, I didn’t take it personally. He’s just venting, but doing it toward the person trying to help you is unhelpful. That’s why I posted here, basically saying to remember that you’re talking to a person, not a punching bag.
In this case, in trying to resolve the issue, he deleted his node_modules directory. So he’s talking about having to reinstall everything by typing npm install and waiting for it to finish.
Yes, and I have a package.json that lists dependencies and the versions I test with. You can force a different version though. I don’t think that’s what happened here. I’m guessing it’s a version of some dependency that should work, because it was released as a minor version within the range I specified, but doesn’t actually work.
It could also be an issue with the build system/bundler, which I can’t really control either.
It’s a frontend JavaScript UI library. I can’t control what other dependencies people install alongside my library, or even whether they follow my library’s dependency list.