Second and higher order npm dependencies are not fixed up for local registry #339

Open
opened 2023-04-17 19:01:17 +00:00 by dboreham · 1 comment
Contributor

Our yarn.lock file fixup logic does not properly handle dependencies that are transitive, not mentioned in package.json.
This is a side effect of a fix for a different problem a few weeks ago when we changed from scanning yarn.lock and instead only use package.json to look for local dependencies.

Our yarn.lock file fixup logic does not properly handle dependencies that are transitive, not mentioned in package.json. This is a side effect of a fix for a different problem a few weeks ago when we changed from scanning yarn.lock and instead only use package.json to look for local dependencies.
Author
Contributor

The result is that any such transitive dependency (e.g. @lirewine/crypto used in laconic-console) will not get fixed up and will be fetched from the location stipulated in yarn.lock.

The result is that any such transitive dependency (e.g. @lirewine/crypto used in laconic-console) will not get fixed up and will be fetched from the location stipulated in yarn.lock.
This repo is archived. You cannot comment on issues.
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#339