Is there anyway to force PNPM to resolve only a single copy of a package?

[lfloyd117]

For some background we use PNPM to manage a monorepo of Ember.js addons, engines & apps.
We are trying to upgrade to Ember's new build system but it complains about some package resolution from PNPM. We get many errors for mismatched peer dependencies along the lines of:

[email protected] -> @myOrg/[email protected]
    sees peerDep [email protected]
      at /path/to/monorepo/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]__@[email protected][email protected]/node_modules/ember-source
    but [email protected] is using [email protected]
      at /path/to/monorepo/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]__@glint+te_d57u3ixfkr4qimpfqyd7ephogm/node_modules/ember-source

Despite ember-source being the same version (4.12.4) everywhere, Embroider cannot resolve it due to it being resolved to a different copy of [email protected] within node_modules/.pnpm.
Personally this seems like more of an issue with Embroider to me, but a maintainer disagrees, so I am seeing what I can do PNPM-side.

I have tried pnpm dedupe, I have completely wiped the lockfile and started over, declared the version in pnpm.overrides etc. I will always get multiple resolutions of [email protected].

Is there anyway to force PNPM to resolve a package to only a single copy to avoid issues like this?

[lfloyd117]

Created a feature request for this here: #8502