Q: Yarn 2 (Berry) fiasco

[leonkosak]

Besides huge braking change (PnP), Yarn 1.x will be archived in a year or two.
https://dev.to/arcanis/introducing-yarn-2-4eh1

Video on Yarn 2 topic: https://www.youtube.com/watch?v=bPae4Z8BFt8

For Angular GUI project - what will you do? NPM did a huge step forward since you were "forced" to use Yarn (lockfile, major speed improvements,...).

[hikalkan]

Thanks @leonkosak for sharing this.
We will check & discuss it again in the next weeks. We will also see the trend of the community.

[leonkosak]

@hikalkan, when this will be actual, consider Deno. Maybe when Yarn v1.22.4 will become EOL, Deno will be stable and feature-rich enough.

[hikalkan]

We were internally discussing to stop suggesting the yarn and turn back to the npm by default.

@armanozak can you briefly write your thought on that?

[armanozak]

Hi @leonkosak,

We believe, Yarn 2 is a completely different package manager and we are not planning to use it. We are waiting for npm v7 release to leave Yarn behind and are hoping this will be the smoothest transition.

I know what Deno is, but cannot see how it is related. Could you please elaborate on that?

[leonkosak]

Moving away from node runtime (and "ecosystem").
But I agree, npm v7 is currently much better option for quicker migration.

[merceyz]

Besides huge braking change (PnP)

Yarn 2 supports node_modules even better than Yarn 1 did, the breaking change was switching the default from node_modules to PnP. You can easily switch back using yarn config set nodeLinker node-modules

[MichelZ]

With NPM7 now being GA for more than a Year, what's the current stance on this issue? @hikalkan