Yarn installing multiple versions of the same package

Question

I have angular in my dependencies at 1.5.11:

{
    "dependencies": {
        "angular": "1.5.11",
        "angular-foundation": "0.7.0"
    }
}

angular-foundation happens to depend on angular@>=1.3.0.

Why does Yarn install angular@1.6.9 as a nested dependency of angular-foundation instead of using the project's version? This causes angular to exist twice in the app and doesn't work properly:

node_modules angular (1.5.11) angular-foundation (0.7.0) node_modules angular (1.6.9)

This doesn't happen with npm@5.6.0 - npm uses 1.5.11 for both the app and the package.

score 25 · Accepted Answer · answered Mar 06 '18 at 08:42

You need to use Yarn resolutions for this

https://yarnpkg.com/lang/en/docs/selective-version-resolutions/

So your package.json will become like this

{
  "name": "depdencies",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",

    "dependencies": {
        "angular": "1.5.11",
        "angular-foundation": "0.7.0"
    },
    "resolutions": {
      "**/angular": "1.5.11"
    }
}

Which tells yarn that any child angular dependency will be set to 1.5.11. After updating this run below

$ rm yarn.lock
$ yarn

Deleting the yarn.lock is generally not advised, especially on big/"old" projects. The documentation you link advises to only run `yarn install` afterwards — François, Jul 04 '23 at 10:16

score 20 · Answer 2 · answered Nov 05 '20 at 03:33

20

https://classic.yarnpkg.com/en/docs/cli/add/#toc-yarn-add-alias

yarn add <alias-package>@npm:<package>

yarn add react17@npm:react@17

answered Nov 05 '20 at 03:33

iugo

415
4
8

3

Please add some explanation to your answer. – Procrastinator Nov 05 '20 at 06:43
2

the explanation is here https://stackoverflow.com/questions/26414587/how-to-install-multiple-versions-of-package-using-npm – Saiqul Haq Dec 16 '20 at 01:41

Yarn installing multiple versions of the same package

2 Answers2