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
You may not set an override for a package that you directly depend on unless both the dependency and the override itself share the exact same spec. To make this limitation easier to deal with, overrides may also be defined as a reference to a spec for a direct dependency by prefixing the name of the package you wish the version to match with a $.
{"dependencies": {"foo": "^1.0.0"},"overrides": {// BAD, will throw an EOVERRIDE error// "foo": "^2.0.0"// GOOD, specs match so override is allowed// "foo": "^1.0.0"// BEST, the override is defined as a reference to the dependency"foo": "$foo",// the referenced package does not need to match the overridden one"bar": "$foo"}}
JamieMason
changed the title
Not happy with $pkg in overrides
feat(versions): add support for pnpm's $pkg keyword
Aug 1, 2024
JamieMason
changed the title
feat(versions): add support for pnpm's $pkg keyword
feat(versions): add support for $pkg keyword
Aug 1, 2024
Description
When you use
$pkg
as the version in pnpm overrides, which should just use the version specified independencies
, syncpack is unhappy.Suggested Solution
replace $pkg by the package's version when comparing versions.
Help Needed
no idea where to start
The text was updated successfully, but these errors were encountered: