With yarn --verbose --frozen-lockfile --production, while building a Docker image (i.e. on a machine where yarn never run), I see yarn performs the GETs relative to packages added as devDependencies not only for those added as dependencies.
In the end yarn correctly installs only dependencies as expected, but I'm wondering if there is some resources and time wasting to performs such GETs.
Is there some reason I do not understand to fetch devDependencies when --production is specified or this can be considered as a minor bug?
Self-service
Describe the bug
With
yarn --verbose --frozen-lockfile --production, while building a Docker image (i.e. on a machine where yarn never run), I see yarn performs theGETs relative to packages added asdevDependenciesnot only for those added asdependencies.In the end yarn correctly installs only
dependenciesas expected, but I'm wondering if there is some resources and time wasting to performs suchGETs.Is there some reason I do not understand to fetch
devDependencieswhen--productionis specified or this can be considered as a minor bug?Thank you
To reproduce
git clone git@github.com:iccicci/cardano-localnet.gitgit checkout yarn-issuemakeThe output is also saved in
build.log.Environment
Both inside and outside the
docker build.