CODEWITHSUNDEEP
yarnpkgmonorepoyarn-workspaces
Jeanluca Scaljeri
Jeanluca Scaljeri

Reputation: 29139

nohoist with workspaces still hoisting

Inside my Monorepo I have one packages in which I want all the dependencies inside its node_modules.

But whatever I do, it's node_modules remains empty.

So, for the purpose of my question I was able to reproduce the issue with the following setup

/
 package.json
 lerna.json
 node_modules
 packages/
          A/
            node_modules
            package.json
            index.ts
          B/
            node_modules
            package.json
            index.ts

I've created a repo for this!

Main package.json

{
  "name": "A-B-test",
  "private": true,
  "workspaces": {
    "packages": ["packages/*"],
    "nohoist": [ "**/B" ]
  },
  ...
  "devDependencies": {
    "lerna": "^3.13.4"
  }
}

B/package.json looks like

{
  "name": "@scaljeri/B",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "dependencies": {
    "angular": "^1.7.8"
  },
  "devDependencies": {
    "browserify": "^16.2.3",
    "typescript": "^3.5.2"
  }
}

Now when I run yarn in the root of the project, all dependencies are installed in the root node_modules.

yarn version: 1.16.0 node: 12.4.0

Any suggestions what might be the problem?

Upvotes: 31

Views: 26631

Answers (5)

James
James

Reputation: 432

The only thing that worked for me on yarn 3.6.4 was adding nmHoistingLimits: workspaces to my root .yarnrc.yml file

Upvotes: 2

Erasmus
Erasmus

Reputation: 654

In my experience, it has been necessary to doubly specify each package in the following manner:

{
  "nohoist": [
    "**/B",
    "**/B/**",
    "**/C",
    "**/C/**"
  ]
}

In addition, I have found it necessary to delete all existing node_modules folders after modifying the nohoist settings. So, if your projects are in packages, and you are in your project directory, you can delete all of those node_modules folders like this:

# delete node_modules on linux
rm -rf ./packages/*/node_modules
rm -rf ./node_modules

# install again
yarn install --check-files

Upvotes: 42

teddav
teddav

Reputation: 664

I tried a few options but the only one that finally worked for me was specifying the nohoist option in the child package. No need to specify anything at the root level.
So my package.json in B package is:

{
...

  "workspaces": {
    "nohoist": ["**"]
  },

...
}

Upvotes: 25

Muho
Muho

Reputation: 3536

If you want to exclude package B node modules from hoisting you can do that in you package.json:

  "workspaces": {
    "nohoist": [
      "**/B",
      "**/B/**"
    ]
  },

after that remove node_modules and yarn.lock and run yarn install again now you should see packages/B/node_modules not being hoisted to the top level of the project

Upvotes: 0

rt_
rt_

Reputation: 1195

Applying the nohoist to the child package's package.json did it for me.

  "workspaces": {
    "nohoist": [
      "*react-native*",
      "*react-native*/**"
    ]
  },

Upvotes: 6

Related Questions