Creating packages for UPM and serving them over a scoped registry

Hi i currently investigate switching to UPM for our inhouse tooling.
I set up a npm registry (Verdaccio) and uploaded a test package. Which shows up in the UPM without any trouble.
But when downloading the package i get this error:

Read only asset Packages/com.company.product./Editor has no meta file.

Seems like Unity wont generate .meta files for the imported package.
Interestingly, when i import the package via ‘Add package from disk…’ it will create those .meta files for me.

So why is this behaviour so different? Is this a bug or do i have to add .meta files to a package when i want to import it via registry?

Hello @Reeley , you might start by checking out our documentation on importing Asset Packages into Unity: Unity - Manual: Asset packages

I hope this helps!

Hey thanks for the reply, but im not entirely sure what Standard asset package have in common with UPM packages. Arent those two different concepts?

Im talking about those here: