Uuuh, I had missed this one :eyes: The fact it's m...
# javascript
e
Uuuh, I had missed this one 👀 The fact it's mentioned we can possibly plug-in any package manager opens up to the use of PNPM where perf is critical. Very nice! https://youtrack.jetbrains.com/issue/KT-64119
a
I missed this too. Was your problem solved after opting out of yarn?
e
Well it's not yet delivered, so can't say. I'd prefer to have it solved in Yarn tho, before switching. When I first setup our monorepo I explicitly avoided PNPM as I wasn't sure about integrating a Kotlin codebase in that monorepo. But if using a custom package manager plugin will be possible, I'd look at using PNPM instead of npm + Yarn, the speed difference is just... massive.
Overall I'm happy K/JS is moving away from Yarn, I suppose a part of the rationale was that Yarn Classic is becoming too old and not widely used, but maybe I'm wrong @Ilya Goncharov [JB]?
What I see normally used is npm, or pnpm nowadays.
a
Either way, more options for us. Can't wait to test your pnpm speed theory with the KGP
e
If I can shave off just 10 seconds on our CI pipeline because of faster deps install/update, that's still a win
i
Since 1.9.23 and Beta4 you can opt-in into using of NPM, it is right. I tried to make ala plugin mechanism, to do it possible to implement support of other package managers. And actually, both NPM support and Yarn support internally are using such mechanism. So it can be considered as POC this approach is working. As for pnpm and yarn berry, there are some problems with integrating them (mainly that
node_modules
are in fact differs from what Node.js could expect) It can be worked with anyway, but for now I have concentrated to just implement NPM support. I guess that via new package manager api pnpm and yarn berry could be impelemented
e
Appreciate the focus on npm. It has gotten faster, more than Yarn Classic as far as I know. So that's nice to have. No rush with pnpm, happy to be a beta tester first and report issues, if any.
👍 1
🙏 2
👍🏾 1