bug: Solving sibling dependencies in a monorepo via cli
robiness opened this issue · comments
Is there an existing issue for this?
- I have searched the existing issues.
CLI Version
0.0.2+1
Project ID
c1d0e2fd-dc3b-4894-be02-e114e1d7d4d7
Description
In a mono repo i get an error when deploying a project with a dependency on an other local package out of it's own scope (siblings in this case)
repo structure:
app(flutter)shared(dart)server(dart)
The 'app' and server depend on shared and are globe projects.
Error on deployment of the projects:
Resolving dependencies...
Because app depends on shared from path which doesn't exist (could not find package shared at "../shared"), version solving failed.
How would one deploy two projects within the same codebase? Especially when local dependencies aren't in the projects scope?
Steps to reproduce
I created a minimal version.
- Clone the repo
- run
globe deployat eitherapporserver, both having a dependency on shared.
Expected behavior
globe deploy should run smoothly with a local dependency out of its own scope.
Screenshots
No response
Additional context and comments
No response
It seems this is more a feature request to have the cli support monorepos.
I can set up both deployments via the dashboard to be auto deployed on pushs to branches. This works for now.
I am not sure what the exact expected behavior is.
Please feel free to close or let me know if it makes sense to create a new feature request for the cli to support mono repos.
@robiness we've made some changes to our build pipeline which should now allow monorepo without melos.
Example project: https://github.com/lesnitsky/globe_example_monorepo_no_melos.