You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 theGET
s relative to packages added asdevDependencies
not only for those added asdependencies
.In the end yarn correctly installs only
dependencies
as expected, but I'm wondering if there is some resources and time wasting to performs suchGET
s.Is there some reason I do not understand to fetch
devDependencies
when--production
is specified or this can be considered as a minor bug?Thank you
To reproduce
git clone [email protected]:iccicci/cardano-localnet.git
git checkout yarn-issue
make
The output is also saved in
build.log
.Environment
yarn run v1.22.19 error Command "dlx" not found.
Both inside and outside the
docker build
.The text was updated successfully, but these errors were encountered: