I see that support was added for NPM in Kotlin 2.0...

# javascript

[eygraber]

I see that support was added for NPM in Kotlin 2.0 RC1. Is there any benefit to using that over yarn (my only interaction with yarn is running the update yarn task occasionally when the build tells me to)?

[Edoardo Luppi]

Yarn Classic is pretty much dead. Switching to npm allows you to streamline package manager, e.g., if you're working in a monorepo.

But the point is this is a starting point. A pluggable system means we could use other package managers in the future.

[eygraber]

I'm coming from the perspective of not "using" any package manager, i.e. I don't interface with it directly; only opaquely through Kotlin.

From that perspective is there any difference? Is it faster, more secure, etc... Something to justify switching to it vs staying with yarn as the default?

[Oleg Yukhnevich]

No need to download yarn
No need to use unsupported technology

[eygraber]

Wouldn't npm also have to be downloaded?

Will npm become the default in a future release and I'll have to do the work to migrate at some point anyways?

[Oleg Yukhnevich]

Npm is included in nodejs, which downloaded anyway :)
Regarding future plans - I don’t know :)

[Edoardo Luppi]

Wouldn't npm also have to be downloaded?

Need to verify but there might be an option to use a global installation. But yes, it's downloaded by default.

Will npm become the default in a future release

Yes

[Edoardo Luppi]

Yarn Classic has many problems. It's deprecated, and it's slower than npm at this point.

[eygraber]

Ok I'll give it a shot 😄

[Edoardo Luppi]

My plan is to move to npm to have a single package manager instead of Yarn & npm.
And then at some point it would be cool to have support for pnpm.