You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
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:
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]
withinnode_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?
Beta Was this translation helpful? Give feedback.
All reactions