Registry system issues

[RobbieTheWagner]

👋 Hello!

I have been working to convert addons to use the newest blueprints, and have been hitting some issues. Since we have to define all the modules, there are edge cases where an addon might have a peerDep of another addon and that addon might have a dep of another addon and so on and so forth.

This creates issues with buildRegistry because every single thing has to be accounted for in vite land, and so the addon has to include things from every addon down the chain. I think instead the addon should only care about its direct dependencies at most, but ideally we could get compatModules working to just add magic in all the way up the chain, except for files your addon actually owns.

[NullVoxPopuli]

Notes for me fixing compat-modules:

• default modulePrefix of ./ when in a v2 addon or when modulePrefix can't be found

[ef4]

I hadn't seen that buildRegistry is a thing. I agree we don't want that pattern at all. Instead, the v2 addon blueprint should have a compatModules feature just like apps have so that you don't need to manually manage all your transitive dependencies.