The code in the Client repo is rather expansive, containing both core utilities/infrastructure and custom features. This combination can lead to circular dependencies. A short term (and possibly long term) solution is to break up this code into sub packages. This would allow the core/infrastructure code to be required independently from the application code.
An alternative would be to pull the core/infra code into a separate repo.
The code in the Client repo is rather expansive, containing both core utilities/infrastructure and custom features. This combination can lead to circular dependencies. A short term (and possibly long term) solution is to break up this code into sub packages. This would allow the core/infrastructure code to be required independently from the application code.
An alternative would be to pull the core/infra code into a separate repo.