Globs support for defining packages in workspaces

[spydon]

I think this is already planned, but I'm opening an issue so that it can be tracked.

Adding globs support will:

• reduce a lot of user mistakes (like forgetting to add new packages to the workspace)
• make migrations from the current melos version to the future melos version where packages are instead defined in the workspace much easier, since their current definitions could just be moved from melos.yaml to the workspace config file

Design doc discussion: https://docs.google.com/document/d/1UEEAGdWIgVf0X7o8WPQCPmL4LSzaGCfJTM0pURoDLfE/edit?resourcekey=0-c5CMaOoc_pg3ZwJKMAM0og&disco=AAAA9uS5yhA

[jonasfj]

I think add globs in workspace: might be nice, but perhaps it is a follow up enhancement. While it does seem feasible, it definitely will involve some work making sure we can still efficiently validate package_config.json using timestamps.

At-least I don't want it to block launching :rocket:

[spydon]

At-least I don't want it to block launching 🚀

Makes sense, I think we'll wait with putting up a migration from Melos to Melos + workspaces until this is done then. Because it will be quite a painful experience for all projects with more than a few packages.

[sigurdm]

Yeah - I don't think this will make it for 3.6 .