Trivikram Kamat

I noticed this issue again during yarn version update. It'll be helpful is yarn updates version in devEngines field, if the project already uses it.

I'm visiting this issue from an old issue I'd reported on `n` node version manager https://github.com/tj/n/issues/784 What are the remaining action items on this request? Is the cache purging issue...

> we are waiting on https://github.com/nodejs/build/pull/3620 to be merged and deployed onto the www server The PR https://github.com/nodejs/build/pull/3620 is merged. Who's going to deploy it and test the full pipeline,...

> yarn config v1.22.21 This appears to be an issue with yarn classic which is frozen https://github.com/yarnpkg/yarn

> The current alternative is to use `yarnPath` This usually requires yarn binary to be present in the repository, and many people didn't like the idea of adding a binary...

Socket Security wrote a blog post summarizing decision from Node.js PMWG ([Package Maintenance Working Group](https://github.com/nodejs/package-maintenance)) https://socket.dev/blog/node-js-takes-steps-towards-removing-corepack

Corepack added support for `devEngines` in https://github.com/nodejs/corepack/pull/643, and released it in [v0.32.0](https://www.npmjs.com/package/corepack/v/0.32.0). The [npm trends](https://npmtrends.com/corepack) show that when there was an issue with downloading pnpm package manager version from corepack...

I believe the code change needs to be made in Manifest.ts https://github.com/yarnpkg/berry/blob/a3e5695186f2aec3a68810acafc6c9b1e45191da/packages/yarnpkg-core/sources/Manifest.ts#L825-L827

npm v10 currently emits warning during publish ```console 🦋 error npm WARN publish npm auto-corrected some errors in your package.json when publishing. Please run "npm pkg fix" to address these...

The request in this issue is not to format `package.json#bin` from object to string when running yarn install. If the repository uses string for `package.json#bin`, there's no change needed. Right...