At the moment we're using yarn v1 for package management in GLSP.
Yarn v1 is quite old and has a lot of known bugs. Even the yarn maintainers themselves advocate switching to the latest versions of yarn (v3 and/or v4) which uses different package management concepts by default. Since the introduction of yarn, the default Node package manager npm caught up in features and stability and is generally preferred. However there are also alternatives like pnpm which again uses a different package management concept.
It should be evaluated which package manager is the new best fit for GLSP. Criteria are at least popularity, maturity, feature set, outlook in the future and migration effort for the GLSP repositories and potentially downstream consumers.
At the moment we're using yarn v1 for package management in GLSP.
Yarn v1 is quite old and has a lot of known bugs. Even the yarn maintainers themselves advocate switching to the latest versions of yarn (v3 and/or v4) which uses different package management concepts by default. Since the introduction of yarn, the default Node package manager npm caught up in features and stability and is generally preferred. However there are also alternatives like pnpm which again uses a different package management concept.
It should be evaluated which package manager is the new best fit for GLSP. Criteria are at least popularity, maturity, feature set, outlook in the future and migration effort for the GLSP repositories and potentially downstream consumers.