-
-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When used with Lerna, a cache directory is created in several different locations #82
Comments
@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 |
Close in favor sindresorhus/find-cache-dir#14 |
@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 |
@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. |
MacOS v10.14.3
v10.15.0
6.7.0
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 rootnode_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 withterser-webpack-plugin
with thecache
flag set to true. This generates a newnode_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:
The text was updated successfully, but these errors were encountered: