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
I have a package I patched (e.g. "resolutions": { "foo@1.2.3": "patch:foo@npm%3A1.2.3#./<path>" }
I'd like to set a resolution for one of its transitive dependencies
normally any of these would work:
"resolutions": {"foo/bar": "4.5.6",// or this"foo@npm:1.2.3/bar": "4.5.6"}
but with the patch, I can't specify "foo@npm:1.2.3/bar" because it's no longer the same package identifier, and bar remains the same old version. I have multiple versions of foo in the project so it's essential that I specify the correct version.
is there a proper syntax to point to the patched package identifier? with yarn why foo I see something like
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
Uh oh!
There was an error while loading. Please reload this page.
-
I have a package I patched (e.g.
"resolutions": { "foo@1.2.3": "patch:foo@npm%3A1.2.3#./<path>" }
I'd like to set a resolution for one of its transitive dependencies
normally any of these would work:
but with the patch, I can't specify
"foo@npm:1.2.3/bar"
because it's no longer the same package identifier, andbar
remains the same old version. I have multiple versions offoo
in the project so it's essential that I specify the correct version.is there a proper syntax to point to the patched package identifier? with
yarn why foo
I see something likeSo maybe a way to identify
foo
with the7a108
hash?I also tried patching
foo/package.json
with a pinned version ofbar
but that didn't have any effect.Beta Was this translation helpful? Give feedback.
All reactions