-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feedback - can every app/lib have their own package.json? #3023
Comments
Yes, you can have multiple We strongly recommend using a single |
I need per app package.json is for solving some problems.
|
Find something related to at #1777 |
Hi there how would you configure this so each application can have a package.json in the monorepo setup? I need this in order to configure integration with an existing CI/CD pipeline that performs the build off changes to the Repo on a project. |
Some of us do not find it a good idea to use a single package.json for all the apps sorry. Could you please help us with some instructions on how to maintain separate package.json for separate apps. |
@FrozenPandaz
Given that I may understand some people may still want to have single package.json for simplicity but IMO this breaks flexibility and separation of concerns. I don't see any valid point in forcing people to use single package.json as the main approach in their projects. Please give us an option to be able to separate the package.json per app and still benefit of all the nx features. Thank you! |
@FrozenPandaz Any updates?? |
@viktornord makes sense |
I've gone with the recommended method of putting a single package.json for all my apps/libs. However I don't feel comfortable not knowing which packages each app is relying upon. Is there a way to figure that out, if I ever decided to move an app into a different standalone project? |
Enforcing a single version is not the same thing as providing the same dependency set to everything. I am looking at multi-module monorepos to avoid depending on anything framework related in core components, which can be packaged in different apps. |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
This is a feedback. I using nx and it works very well to my clients :)
One thing though, currently I have one
package.json
with many dependencies of my apps and libs and its hard to tell which dependency in use in which apps/libs.It will be great if each app and lib will have its own package.json with the packages that app/lib uses.
Even all dependencies are the same versions, I want to know in ease what packages I use for the app.
Why? sometimes I want to move the apps from repo to another repo and I need to take the
package.json
and copy and filter the packages that the app/lib not use.(In lerna monorepos for example I have each package the package.json`)
NX Team, what do you think about it? this can be done in nx?
The text was updated successfully, but these errors were encountered: