I just wanted to share this insightful comment on Reddit.
I've seen HelpDesk technicians at work asking,
"Have you tried switching it off and on again?"
several times a day, thus I bursted into laugher.
Please feel free to share if you think of any others ๐
Top comments (11)
It can get even worse. There was a time at work where we were struggling to get people to all use the same npm version. One of the developers put this in the scripts section of our package.json:
"relock": "rm -rf node_modules/ && rm package-lock.json && npm i"
It sounds like that's the problem
npm citries to solveRelated to the original response, npm 6 now allows you to run
npm ciWhich deletes the node_modules and installs the exact version mentioned in your lock file. This is a great way to reproduce the exact working copy of your node app.
Yeah! It mostly is, but the subtle difference was our package-lock.json files were out of sync. We were just having a hard time getting everyone on the same version of npm, so the
package-lock.jsonfiles generated bynpm installwere slightly different.npm ciruns based off ofpackage-lock.jsonNow I see what you means.
While
npm citries to make library to be consistent across computers,relockcommand installs libraries from clean slate.Related to the original response, npm 6 now allows you to run
npm ciWhich deletes the node_modules and installs the exact version mentioned in your lock file. This is a great way to reproduce the exact working copy of your node app.
Thanks for the tip Kushan.
Even this morning, I've deleted
node_modulesfolder manually...npm ciseems like a great addition to the CLI. ๐Today it took me way too long to remember that most of the internet works on a variant of this principle:
"Try switching it on and off again, then wait several hours."
๐ Takes a while for DNS records to propagate.
That's probably the easiest way to let non-technical people to wait just long enough ๐
Just throwing it out there: my previous job was a Technical Advisor for a Mobile Phone Insurance Company. Statistically, the fix most likely to work was legitimately turning it off and on again!
Seems like data don't lie
๐
Without doubt, It works!) That's what experience says