Why is npm on windows so fucking horrible. Every fucking time I have to use npm on Windows I encounter a myriad of fucking issues. On MacOS it just seems to fucking work.

FUCK!

It seems horrible to me everywhere.

Solution: don’t use Windows

Never had many problems....

not sure if it is npm or windows 🤣 I am using only linux

@rim01 I'm pretty sure it's Windows here given how much shit can hit the fan when using CLIs (e.g. npm, ng and vue) on Windows terminals when those work perfectly fine on GNU/Linux distros.

npm is the source of much distress nonetheless, but Windows just adds an extra layer of shit on top

@ars1 I use yarn these days for everything.

@rim01 I wish I had a say on the environment I wrote my software in when I work for large enterprises - instead I'm remote desktoped into a remote desktop that remote desktops into a remote desktop that remote desktops into a remote desktop that remote desktops into a remote desktop.

@Berkmann18 Exactly man.

@100110111 Heh. Agreed.

@N00bPancakes You must be one of the lucky ones :P

Most likely because windows filesystem operations are super slow compared to ext4 on macos.

Also, npm shims most of its code to work on windows, whereas it's originally designed for unix-like systems (macos included).

Also, everyone at npm develops on a macos - at least, they did when I knew them and visited their offices - just like most of silicon valley.