package.json: Why not use "packages/**" to support nested workspaces? #13013
kynikos
started this conversation in
Show and Tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I haven't been able to find an answer to this, but I can't be the first to have a project with nested workspaces, for example:
package.json
(B)Nx seems to initialise
package.json
(A) like this:However in that way
npm install
will not install the dependencies inpackage.json
(C).Changing
package.json
(A) to this solved the problem for me:Why doesn't Nx initialise
package.json
(A) to usepackages/**
from the start? Are there downsides to that?Beta Was this translation helpful? Give feedback.
All reactions