Hi, I'm experimenting with a project setup where I write Feature Modules in isolation. It's an architectural benefit in that it isolates features, promotes testable code, and promotes simpler feature re-use between projects. This is easy to support in the manifest, as I can add a file path to the local module dependency. Working with the new Netcode and Testing suite, however, for each feature I have four modules (client, mixed, server, tests), and this makes the manfiest rather messy. It would be very nice to be able to set up a hierarchy of modules, so that for each feature I could have a root package that had dependencies to the four packages of that feature. But I noticed that dependencies in packages only support the semantic versioning dependencies, and not file or url paths. Is there any way I can go about adding this kind of hierarchical dependencies in my local packages? Do I have to use scoped registries? For this type of problem it feels a bit overkill? Thank you.