Apparently it works retroactively and now you are on Windows.
Oh man, that would be a hell of an easter egg if it cleared your terminal and pretended to be a dos prompt
deploys your code to your dev environment
Hope you didn’t have the repository URL in your package.json… otherwise it’ll be gone now.
You forgot to run
npm edge devfirstYou’ll be forced to use only Windows forever.
Source: Homestar Runner - Strong Bad Email #50 - 50 Emails
https://homestarrunner.com/sbemails/50-50-emails
https://www.youtube.com/watch?v=7rrZ-sA4FQcDid you get four hundred thousand viruses?
Computer over?
Virus = very yes?That’s not a good prize!
Hi 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
Nothing, it’s already ruined(!)
dev.ruin()!
SyntaxError: Unexpected ! operatorNo, it’s an order!
Understood
The NPM gods will smite you for using CMD instead of PowerShell.
believe it or not, jail.
We have the best deployment pipeline in the world, because of jail.
i think the dev is already ruined having to use npm
Security people will say so.
You may have to switch to a proper operating system to redeem yourself.
“ruin dev” is redundant; that’s the default behavior.
Npm ruined dev long before you tried this.
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!
Considering “being ruined” is a state, and not a scale, the dev is already ruined, because it’s not Linux.
