When used with Lerna, a cache directory is created in several different locations

[damienwebdev]

• Operating System: MacOS v10.14.3
• Node Version: v10.15.0
• NPM Version:6.7.0
• Webpack Version:

@angular-devkit/build-angular@0.13.1
  ├── terser-webpack-plugin@1.2.2 
  └─┬ webpack@4.29.0
    └── terser-webpack-plugin@1.2.2  deduped

Expected Behavior

When using lerna for hoisted package management in a monorepo, when I do run lerna run build and it runs the build script in each of my packages, the resulting cache directory should be in my root node_modules of my project.

Actual Behavior

When using lerna for hoisted package management, when I do run lerna run build and it runs the build script in each of my packages, ng build runs webpack with terser-webpack-plugin with the cache flag set to true. This generates a new node_modules directory in each of my source directories.

How Do We Reproduce?

You can reproduce fairly easily by cloning: https://github.com/graycoreio/daffodil and then:

npm install -g lerna @angular/cli
lerna run build
look in apps/daffio/ and see a new node_modules folder

[alexander-akait]

@damienwebdev we use https://github.com/avajs/find-cache-dir for detect cache directory, better create issue in their repo, as workaround you can setup path in configuration

[alexander-akait]

Close in favor sindresorhus/find-cache-directory#14

[damienwebdev]

@evilebottnawi See @sindresorhus 's comment I don't think there are any plans to change this, so I think the next step is to find a different find-cache-dir implementation that allows for configuration, utilize it here, and then make changes in @angular/angular-cli to take advantage of it.

[alexander-akait]

@damienwebdev we provide cache option (https://github.com/webpack-contrib/terser-webpack-plugin#cache), you can implement any behavior. You can add example to docs.