Bug: `peerDependencies` isn't set in the `package.json` published to npm

[kimulaco]

Describe the bug

The package.json in the main branch has peerDependencies set, but the package.json actually published to npm does not have peerDependencies set.

This causes an issue in monorepo apps with multiple vue versions where unintended vue versions are imported.
pnpm/pnpm#8917

To Reproduce

Here's a minimal example:
https://github.com/kimulaco/monorepo-vue-example

The problem will not occur if you overwrite peerDependencies with pnpm's packageExtensions.
https://github.com/kimulaco/monorepo-vue-example/tree/add-peerDependencies

Expected behavior

peerDependencies should also be set in the npm published package.json.

Related information:

❯ npx envinfo --system --npmPackages vue,@vue/test-utils,vitest,jest

  System:
    OS: macOS 14.6.1
    CPU: (8) arm64 Apple M2
    Memory: 110.89 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh

Additional context

[cexbrayat]

Yes this has been fixed in #2511 but not yet released

[kimulaco]

@cexbrayat Thanks.
I misunderstood the order of adding peerDependencies and the previous release.

[kimulaco]

@cexbrayat Is there any planned release date for the next version?

I'm experiencing this issue in my project. While I've temporarily worked around it using the pnpm workspace features, I'm looking forward to having this fix officially released 🙏