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
PNPM supports pnpm.overrides and resolutions only at the root of a project. Ember Try sets it at the closest package.json. In a typical setup of a v2 addon that's the "test-app" package. That does not have any affect. Ember Try must set it in the package.json at the workspace root.
Likely there is a second bug: Ember Try sets overrides at the root of the package.json. That's correct for NPM. But I think for PNPM it must go into a pnpm member. This is an example taken from PNPM documentation:
PNPM supports
pnpm.overrides
andresolutions
only at the root of a project. Ember Try sets it at the closestpackage.json
. In a typical setup of a v2 addon that's the "test-app" package. That does not have any affect. Ember Try must set it in thepackage.json
at the workspace root.Likely there is a second bug: Ember Try sets
overrides
at the root of the package.json. That's correct for NPM. But I think for PNPM it must go into apnpm
member. This is an example taken from PNPM documentation:But Ember Try generates the following, which is valid for NPM but does not fit with PNPM documentation:
The text was updated successfully, but these errors were encountered: