You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that if you're running lix to install a lix project that it updates the projects you have. This is good. However, if you have two projects that make use of the same lix lib there is nothing taken into account. Whatever the last installed libs dependent versions take precedence.
Maybe there should be a way to detect when getting a different version of a library installed to your project that it may introduce a dependency conflict. Or at least after installing it tells you what lix libs have unmet dependencies.
One example where this is a problem is in mvcoconuts react native example. It seems like there's no way to update the dependencies in this project right now without one thing breaking or another. That is, the order in which things depend on what is not really there.. if it could be that is.
The text was updated successfully, but these errors were encountered:
Hello!
I noticed that if you're running lix to install a lix project that it updates the projects you have. This is good. However, if you have two projects that make use of the same lix lib there is nothing taken into account. Whatever the last installed libs dependent versions take precedence.
Maybe there should be a way to detect when getting a different version of a library installed to your project that it may introduce a dependency conflict. Or at least after installing it tells you what lix libs have unmet dependencies.
One example where this is a problem is in mvcoconuts react native example. It seems like there's no way to update the dependencies in this project right now without one thing breaking or another. That is, the order in which things depend on what is not really there.. if it could be that is.
The text was updated successfully, but these errors were encountered: