xtermjs
Replace yarn with npm
npm has long had the performance changes we switched to yarn for. Also we're stuck on yarn v1 (https://github.com/xtermjs/xterm.js/issues/5175) and VS Code has switched back to npm and it would be nice to keep them in sync.
I'd love to work on this issue, but I'd like to ask: what parts of xterm.js use yarn? And since it's already possible to use npm manually, do you mean that we should change the default package manager to be npm instead of yarn?
@GreggZumbari this would be best to be someone on the core team to do as dependencies are a common attack surface for supply chain attacks.
@Tyriar - Could I get clarification on what is stuck -- is it that the yarn.lock file has a full set of dependencies pinned - so that the versions need to be matched?
In my experience, Yarn 4 works well, has greater security features and more flexibility than npm. While this seems to be a closed case, may I suggest looking into developing an appropriate .yarnrc.yml which would bring Yarn up to date? corepack remains a part of the standard node.js distribution, making corepack enable straightforward.
@Downchuck yarn is an extra tool when npm that ships with node is sufficient for our use cases. It may be better in various ways, but it's not that important given our use case.