Package Manager for all?

Hey there!

I see great positive changes at the Package Manager over last betas and today's b2 brings this great beauty to us:



I just can't wait to try out this for own packages as an asset publisher and developer in general.
Are there any possible dates or plans on opening Package Manager for the external packages?

I would love to participate in alpha or beta stage of the open world test if it will exist!

 

Actually I see it's possible to add external packages with some hand work and being guided by awesome docs, but still, it's pretty hacky and some official APIs or tools would be really great to see ^^

 

Nice find, could you explain how you hacked your way to custom packages ?

 

@dzamani
It wasn't that hard actually.
I've prepped my package following the docs (added the package.json to the root folder of my package, added assembly definition as well), created new folder in the cache (C:\ProgramData\Unity\cache\packages\packages.unity.com\net.codestage.maintainer@1.4.1), copied all the files I had in package as is:



And added reference to this package at the [Project Folder]\Packages\manifest.json of the project:

Code (JavaScript):

1. {
2.     "dependencies": {
3.     "net.codestage.maintainer":"1.4.1"
4.     }
5. }

That was enough to let Unity pick it up and compile as a Package Manager package.
There is some issues with paths tho - my editor code is loading images manually and it didn't found them being executed from the such package, I believe this is because I used hacky way of detecting Maintainer folder with MonoScript.FromScriptableObject or like so, I didn't tried to figure out so far.
Code itself works fine tho, the images paths is only one issue I saw in my case.

 

Oh okay, I thought that you managed to add your own registry alongside unity's package registry.
Still, it's nice to see that it's kinda working.

 

@erick_unity, I would like to see package manager can support pulling repo like github so I can always check and get the latest update easily.

 

Yes please iron out all the niggly issues so when we finally get to use it too, it will be hopefully, problem free

 

Well if we could just bypass any security on the registry url (the one you can change inside manifest.json) we could already have some things. I myself don't see how it could be an issue doing that early in the dev process but I guess that there is related issues to doing that.