<@U053Y96LR9U> hey! Now that you've switched to 2....

# io

[Edoardo Luppi]

@Filipp Zhinkin hey! Now that you've switched to 2.0, are you considering switching from Yarn to npm?
If official libraries start switching to npm support, we might find and fix bugs.

[Filipp Zhinkin]

Hey! Are there any benefits from using npm instead of Yarn?

[Edoardo Luppi]

It probably depends on case by case when we talk about speed.

But the main point is Yarn Classic is * dead *, that's why npm support was introduced.

[Edoardo Luppi]

If you have Node installed, transitively you should also have npm, so one less dependency.

[Filipp Zhinkin]

But the main point is Yarn Classic is * dead *

Well, then we probably should start transitioning to npm 🙂

[Filipp Zhinkin]

I'll open the issue then, thanks for pointing to it

[Edoardo Luppi]

Np! The package manager Gradle API is built with extensibility in mind (at least from what I've read here an in YT), so if we collectively start using npm starting from 2.0, we can iron out defects, if any are present

[Edoardo Luppi]

Related issue https://youtrack.jetbrains.com/issue/KT-64119

[Filipp Zhinkin]

https://github.com/Kotlin/kotlinx-io/issues/340

[Adam S]

I recommend not using npm for now - it will fail on Windows machines https://youtrack.jetbrains.com/issue/KT-67442

[Edoardo Luppi]

So basically if I develop on Windows, it will fail on Linux, and viceversa?

[Adam S]

if you generate and save the lockfile on your mac/linux machine, it will work. But if I checkout the project on a Windows machine it will fail

[Edoardo Luppi]

Ah damn! Clear why we've not encountered this issue then, we only use Windows machines

[Adam S]

yeah, if everyone uses the same OS it will work 🙃