Apparently it works retroactively and now you are on Windows.
“ruin dev” is redundant; that’s the default behavior.
Nothing, it’s already ruined(!)
dev.ruin()!
SyntaxError: Unexpected ! operatorNo, it’s an order!
Understood
Your code will be minified and your git history deleted
believe it or not, jail.
We have the best deployment pipeline in the world, because of jail.
You’ll be forced to use only Windows forever.
It’s an alias to start the upgrade to Windows 11… you thought you were being careful all those months dodging the Windows 11 upgrade button but you’ve done it now! Get ready for an objectively worse OS!
You forgot to run
npm edge devfirstdeploys your code to your dev environment
Did you get four hundred thousand viruses?
Computer over?
Virus = very yes?That’s not a good prize!
Source: Homestar Runner - Strong Bad Email #50 - 50 Emails
https://homestarrunner.com/sbemails/50-50-emails
https://www.youtube.com/watch?v=7rrZ-sA4FQcHi Strong Bad
NPM
ruin devis a new advanced feature that endorses opinionated “extreme programming” techniques. First it gets to work rebuilding node_modules, but with all the least compatible module versions in order to accelerate testing. It also minifies your .js code in place, to save you some CPU cycles later. Lastly, it squashes your entire git history on all branches, to save space.It also tries to do
rm -rf /to save more space, but in this case it’s a futile attempt
npm will ruin the dev now. It happened to me 11 months ago
Your .env with production credentials is now up on a public repo
Hope you didn’t have the repository URL in your package.json… otherwise it’ll be gone now.
Not sure CrowdStrike runs on npm, but still ruined it all for sure
