Lukas Klingsbo
Lukas Klingsbo
It is indeed planned, thanks for opening an issue so that we can track it! I'll link in the Flutter design doc for it is here too: https://flutter.dev/go/pub-workspace
Related: https://github.com/dart-lang/pub/issues/4376
Related (globbing in workspace definition, which would make future migrations easier): https://github.com/dart-lang/pub/issues/4391
@Leptopoda I agree, it's not a blocker, possibly we could even write a simple migration script for it.
@xaethos it shouldn't be a problem for them to co-exist already afaik. With the workspaces we can simplify a lot of our code in Melos and remove the packages config...
> I hope `melos bootstrap` will not be removed but tweaked to handle the new workspace changes. > > * This way we can still use `hooks` pre/post `bootstrap` command...
> I don't think so... it just uses a glob in the melos.yaml, right? Correct, there is no caching of the package list when bootstrapping.
The PR to migrate Melos to Pub Workspaces is now out, feel free to review it! (https://github.com/invertase/melos/pull/816) Tomorrow I'll create a pre-release so that you can try it out in...
I just published Melos v7.0.0-dev.1 enabling the Pub Workspaces feature, please try it out so that we can iron out any potential problems! 🙂 https://pub.dev/packages/melos
If you want to add `resolution: workspace` to all of your `pubspec.yaml` files you can do this: ```sh find . -type f -name "pubspec.yaml" -exec sed -i '/^name:/a resolution: workspace'...