all 37 comments

sorted by: hot top controversial new old
[–] 146 points 2 years ago (1 child)

Apparently it works retroactively and now you are on Windows.

  • source
  • hideshow 2 child comments
  • [–] 59 points 2 years ago

    "ruin dev" is redundant; that's the default behavior.

  • source
  • [–] 54 points 2 years ago (1 child)

    Nothing, it's already ruined(!)

  • source
  • hideshow 2 child comments
  • [–] 42 points 2 years ago

    Npm ruined dev long before you tried this.

  • source
  • [–] 38 points 2 years ago*

    Your code will be minified and your git history deleted

  • source
  • [–] 30 points 2 years ago (1 child)
  • [–] 30 points 2 years ago

    You'll be forced to use only Windows forever.

  • source
  • [–] 29 points 2 years ago (1 child)

    i think the dev is already ruined having to use npm

  • source
  • hideshow 2 child comments
  • [–] 26 points 2 years ago (1 child)

    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!

  • source
  • hideshow 2 child comments
  • [–] 20 points 2 years ago (3 children)
  • [–] 20 points 2 years ago

    You forgot to run npm edge dev first

  • source
  • [–] 19 points 2 years ago*

    deploys your code to your dev environment

  • source
  • [–] 16 points 2 years ago (1 child)

    NPM ruin dev is 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.

  • source
  • hideshow 2 child comments
  • [–] 13 points 2 years ago

    You may have to switch to a proper operating system to redeem yourself.

  • source
  • [–] 8 points 2 years ago

    npm will ruin the dev now. It happened to me 11 months ago

  • source
  • [+] 8 points 2 years ago* (last edited 1 year ago)
    [–] 8 points 2 years ago

    Hope you didn't have the repository URL in your package.json... otherwise it'll be gone now.

  • source
  • [–] 7 points 2 years ago

    NPM on Windows, it doesn't matter anymore.

  • source
  • [–] 7 points 2 years ago

    Yeah you’re gonna need a new dev environment. That one’s toast.

  • source
  • [–] 6 points 2 years ago

    Your .env with production credentials is now up on a public repo

  • source
  • [–] 4 points 2 years ago

    Same thing.

  • source
  • [–] 4 points 2 years ago

    Not sure CrowdStrike runs on npm, but still ruined it all for sure

  • source
  • [–] 3 points 2 years ago

    MCP: Already there, Hun! END OF LINE.

  • source
  • [–] 2 points 2 years ago

    Its an alias, so no problem.

  • source
  • [–] 2 points 2 years ago

    You should press backspace. 😉

  • source
  • [–] 1 point 2 years ago

    npm ruin dev running shittier could be a nice prank... depending on how often it gets typed.

  • source
  • [+] 1 point 2 years ago* (last edited 1 year ago)