Open ruyadorno opened 3 years ago
Is this the same reason why I have:
api@ D:\Programming\Projects\x\v4\api
├─┬ @x/type-graphql-extensions@1.0.0 -> .\..\type-graphql-extensions
│ ├─┬ graphql-parse-resolve-info@4.12.0
│ │ └── graphql@15.8.0
├── graphql@15.8.0
(simplified)
After running dedupe?
This is a big issue, since graphql
fails to run when more than one version exists:
Ensure that there is only one instance of "graphql" in the node_modules directory.
Is there any workaround?
@ruyadorno Is there a workaround for this issue? I'm quite blocked by not being able to dedupe graphql.
I wonder if this will be fixed by #4745.
What / Why
When trying to deduplicate versions of a module in a linked dependency, running
npm install
will not work as expected.When
Given a package with a dep@ conflicting with a dep@ in a linked dependency, e.g:
Updating
a/package.json
to list a dependency onabbrev@^1.0.0
will not result in a deduplicated install tree.How
Before manually deduping dep
After manually trying to dedupe and running npm install
Expected Behavior
I expect running
npm install
ORnpm dedupe
after manually tweaking dep version ranges in mypackage.json
files to produced a deduplicated install tree.