To Yarn and Back to Npm Again • Hacker News Board

Re: To Yarn and Back to Npm Again

#31

Post by ljm » Tue, May 29, 2018, 11:47 PM UTC

repsilat wrote: post #20

himom wrote: post #11

Earlier quoted context omitted.

Our experience has been yarn is fast and reliable.

Hmm, `yarn add` reliably takes a few years in my environment (WSL). Maybe the environment is the problem, though.

You need to add an exclusion or two to Windows Defender. The yarn folder in %APPDATA% is one (if you're running yarn locally, same deal for npm), and the path to where you keep your repos is the other (which is a lot easier if that doesn't exist entirely inside your WSL filesystem).

The reason it's so slow is because the virus scanner is running on the insane amount of tiny files a typical JS app will have. Used to take me 30 minutes each time until I did that; it was still slower than Linux/Mac but it was coffee-break slow, not three-course meal slow.

Re: To Yarn and Back to Npm Again

#32

Post by [deleted] » Wed, May 30, 2018, 12:04 AM UTC

bcheung wrote: post #4

I'm not sure I like the new npm. It seems faster but it's annoying to use it with how often it prompts you to update it and all the verbosity, annoying messages about peer dependencies, and now audits that you can't really do anything about. There's just so much noise now. Old version just worked and got out the way.

[deleted]

Re: To Yarn and Back to Npm Again

#33

Post by Untit1ed » Wed, May 30, 2018, 12:08 AM UTC

elvin_d wrote: post #5

Yarn also has a useful feature `workspaces`. With npm have to use lerna for it

This is a massive deal for monorepos. A lerna bootstrap with yarn as the package manager takes a few minutes from scratch, with npm it takes hours.

Re: To Yarn and Back to Npm Again

#34

Post by spraak » Wed, May 30, 2018, 12:35 AM UTC

> We've published an open-source module called deyarn to help you convert your projects from Yarn to npm!

Would have been cool to call it "untie" or "untangle"

Re: To Yarn and Back to Npm Again

#35

Post by jaxn » Wed, May 30, 2018, 12:51 AM UTC

manigandham wrote: post #26

repsilat wrote: post #20

Earlier quoted context omitted.

Hmm, `yarn add` reliably takes a few years in my environment (WSL). Maybe the environment is the problem, though.

The windows subsystem for linux? It's dealing with lots of tiny files going through a virtualization layer, you might want to just use the Windows native version of Yarn which is very fast.

NTFS may not handle a bunch of small files well, but I'm pretty sure WSL isn't a virtuialization layer.

Re: To Yarn and Back to Npm Again

#36

Post by kenning » Wed, May 30, 2018, 1:18 AM UTC

bcheung wrote: post #4

I'm not sure I like the new npm. It seems faster but it's annoying to use it with how often it prompts you to update it and all the verbosity, annoying messages about peer dependencies, and now audits that you can't really do anything about. There's just so much noise now. Old version just worked and got out the way.

> Old version just worked and got out the way.

Just when I thought I had heard every opinion on npm, I find someone with the opinion "It always worked fine."

Re: To Yarn and Back to Npm Again

#37

Post by swrobel » Wed, May 30, 2018, 1:56 AM UTC

reitanqild wrote: post #25

swrobel wrote: post #14

Earlier quoted context omitted.

Here's an issue I've experienced with using upgrade: https://github.com/yarnpkg/yarn/issues/5749

> and I noticed that certain packages were completely missing from the node_modules folder, yet are listed in yarn.lock Sounds like what I'd expect from running yarn clean... (If anyone isn't aware: that command doesn't clean target folders but rather goes crazy inside node_modules.)

Yeah you're misreading my issue

Re: To Yarn and Back to Npm Again

#38

Post by hitekker » Wed, May 30, 2018, 2:00 AM UTC

himom wrote: post #10

jakoblorz wrote: post #2

That's why we love the JavaScript ecosystem so much: you have always got something to do!

Shhhh... mutually-reinforced job security from unnecessary development churn and endless novelty.

Exactly.

I once brought up what you said to an acquaintance and, wow, the way the color drained from his face, the way his voice hardened and lowered in tone, as he said "That's just a bunch of bullshit.". Later that month, he would go to work for IBM as a junior-level front-end engineer.

As always, it's probably better to be quiet and let the insecure live in their own little worlds.

Re: To Yarn and Back to Npm Again

#39

Post by steve_adams_86 » Wed, May 30, 2018, 4:04 AM UTC

jaxn wrote: post #35

manigandham wrote: post #26

Earlier quoted context omitted.

The windows subsystem for linux? It's dealing with lots of tiny files going through a virtualization layer, you might want to just use the Windows native version of Yarn which is very fast.

NTFS may not handle a bunch of small files well, but I'm pretty sure WSL isn't a virtuialization layer.

You're right (I didn't realize this): https://docs.microsoft.com/en-us/windows/wsl/faq#why-would-i...

Re: To Yarn and Back to Npm Again

#40

Post by reitanqild » Wed, May 30, 2018, 4:10 AM UTC

msoad wrote: post #17

Just the way npm handled my bug reports made me decide never use npm cli again. The registry is something everyone has to use because npm has a monopoly. It's not open source and is making money for a for profit company. I'm very disappointed to see Node.js is still shipping this anti-foss OSS with its executables :(

Try running a repo for free : )

As you might infer from my comments I'm not the biggest fanboy but criticising them over running a freely available repo that the community has used for years feels a little bit wrong