Make package.json optional in a mono-repo setup #1611
squiddy
started this conversation in
Ideas & RFCs
Replies: 2 comments 2 replies
-
If you just don't add those dirs to workspaces in the root package.json I don't think those package.jsons are needed. But the idea was to add the production deps to the workspace dirs so they can be deployed separately. Also not sure how resolving works then if you don't deploy the root aswell. |
Beta Was this translation helpful? Give feedback.
1 reply
-
I see package.json is required some places. We could test for them and supply default values if there is no json. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The
with-monorepo
example is similar to what we're doing for our project, however both "razzle apps" share the same set of dependencies that are setup in thepackage.json
of the repository root.Right now, I have to put at least an empty
package.json
into each app's folder. Some testing with the example suggests that there might be two places that require a package.json to be present.I'm wondering if our case is special, or if making that file optional is a worthy goal? Or perhaps, alternatively, have it fall back to the parent package.json?
Beta Was this translation helpful? Give feedback.
All reactions