Support for dependencies with custom scopedRegistry without having to manually add it to manifest?

Hello.

I have been developing several packages lately and I have always encountered the same problem. When my package has an external package dependency (not contained within the Unity repository), the Unity project that imports my package must manually add the scopedRegistry to its manifest.json.

Unity plans to add functionality to allow defining a scopedRegistry within the package.json and then automatically adding it to the manifest.json of the importing project?

Does anyone know of a workaround or snippet that allows such functionality?

1 Like

Unity team? Any insights on this?