Mike McCready

@kayac-chang Yarn (Classic) `v1.22.19` has already been replaced by `v1.22.21`, so any attention should be focussed on this latest version.

@RDIL The following is from WSL2 under Windows 11 with a virtual Ubuntu 22.04.3 environment and nvm as Node manager installed: ```text npm install yarn@latest -g yarn -v 1.22.21 export...

@shashi-appgolive > I m facing same issue while running mongo, this issue resolved ? If you are having a problem with mongo then you should probably be referring to their...

@RDIL Were you now able to reproduce? and if so, is there still an intention to fix the issue in Yarn Classic?

@SeaForeEx > I'm seeing that the way to fix this punycode/userland issue in Node is to change `const punycode = require('punycode');` to `const punycode = require('punycode/');`. I have searched my...

@JJJ > Also still seeing this. That is to be expected, since this issue is still open. It was however great to read https://github.com/yarnpkg/yarn/issues/9013#issuecomment-1888289602 which said: > Update: I spoke...

@basiq-ash > Facing same issue, is there any update on this? The last update is from last week. See https://github.com/yarnpkg/yarn/issues/9013#issuecomment-1888289602

The issue is also reproducible if Yarn Classic is used to set the version to Yarn Modern: ```bash nvm use 21 corepack disable npm install yarn -g yarn set version...

@noxidsoft > `npm run serve` - You can follow issue https://github.com/vercel/serve/issues/789 for the problem you describe. Your comment is in the wrong repository, since this issue is about Yarn, not...

- Also asked in https://github.com/yarnpkg/yarn/issues/9035