Open Leptopoda opened 2 months ago
Hi @Leptopoda 👋 Thanks for opening this issue!
In talking with the team we do believe that this is a valid bug as we have not added in support for Workspaces at this time to any of our packages. The main reason for this is that overall the Workspaces feature is still experimental from the Dart team. This was pointed out by the team in the post announcing the 3.5 release
We believe the fundamental solution is to create a single, shared resolution of the versions of each dependency in such repos, and are working on such a capability via a new pub feature called workspaces. We’ll have much more to share about this in our next Dart release, but for now you can go ahead and see how this was recently applied to the Flutter engine repo.
Given this, I'm going to leave the issue open as it is valid but we won't plan on re-evaluating it until the Workspace feature is complete and fully launched by the Dart team.
Description
dart_frog build
fails when run in a pub workspace package. The issue seems to be that a pub workspace will only generate one globalpbspec.lock
file for the entire repository. Therefore, the post gen hook of thedart_frog_prod_server
mason module fails.Steps To Reproduce
cd packages/api
(the package our server code is living in)dart_frog build
:zap:Expected Behavior
dart_frog manages to build the server code.
Additional Context
For reference, pub workspaces are the new dart native mono repo management, which is currently in preview since dart 3.5. More info at: https://flutter.dev/go/pub-workspace