Open hitech95 opened 1 year ago
I am also seeing this issue
No issue here when using like yarn workspaces focus --production @scope/my-package
from the root cwd
. Yarn install (like it should do) only manifest.dependencies
field for the given workspace. This is the right way for production usage. I never seen this issue from yarn@^3.2.0
to yarn@^3.3.0
for my part.
Self-service
Describe the bug
I have a monorepo with 3 packages one of them depends on the other two (
common
,interfaces
,api
). Each package has its own 3rd party dependencies.When I execture the command
yarn workspaces focus --production
it links/install only some of the dependencies. The rootnode_modules
is empty and in theapi
'snode_module
directory there is no reference to thecommon
andinterfaces
packages.If I use instead
yarn install
all works fine but there a are a lot of "useless" dependencies installed aswell.It is showing this issue also with external dependencies, for example:
To reproduce
he nodeLinker option in .yarnrc.yml is set to node-modules A simplified package.json are:
/package.json
/packages/common/package.json
/packages/api/package.json
Environment
Additional context
No response