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
believe it or not, jail.
We have the best deployment pipeline in the world, because of jail.
Hope you didn’t have the repository URL in your package.json… otherwise it’ll be gone now.
Nothing, it’s already ruined(!)
dev.ruin()!
SyntaxError: Unexpected ! operatorNo, it’s an order!
Understood
npm will ruin the dev now. It happened to me 11 months ago
You may have to switch to a proper operating system to redeem yourself.
“ruin dev” is redundant; that’s the default behavior.
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.
The NPM gods will smite you for using CMD instead of PowerShell.
i think the dev is already ruined having to use npm
Security people will say so.
You’ll be forced to use only Windows forever.
Same thing.
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
MCP: Already there, Hun! END OF LINE.
Npm ruined dev long before you tried this.
