search

beeman / nestjs-typeorm-nx

14 stars 5 forks source link

Lerna / Multiple package.json Files #3

Open johannesschobel opened 5 years ago

johannesschobel commented 5 years ago

Dear @beeman ,

and another question, i recently stumbled upon. How do you deal with multiple package.json files? With nx you have one main package.json in the root folder, every dependency of the project is stored there. However, you may want to add the dependencies to the apps, or the libs where they are "consumed" / needed.

I know that you can achieve this with a combination of lerna and yarn workspaces quite easily.

What do you think about this in general? Is it just me that thinks this may be quite useful? Or is it some kind of "bad behaviour" to have different package.json files in a mono-repository?

Actually, the combination of lerna & yarn workspaces would solve the issue that you need to migrate every package to the same version of a dependency. For example, two libraries can consume the same package in different versions, so you can migrate one lib after another one..

What is your opinion on this? Maybe you can give some insights from one of your larger nx projects? All the best and thanks for your time and help

johannesschobel commented 5 years ago

or will this get "out of hand" so quickly if you have multiple libs, that it is practically not maintainable any more?