Version: 2022.3
Feature sets



When you have finished developing your package and you want to share it with other users, you have several options:

Compressed file You can distribute a zip file to other Unity users. That way, they can decompress the zip file to a local folder on their own computer and install the package from disk.
Tarball You can distribute a tarball to other Unity users. That way, they can install the package from the local tarball directly.
Git URL 可以使用以下支持的协议之一分发指向您的 Git 代码仓库的链接。然后,用户可以使用包的 Git URL 来安装包,因为 Unity Package Manager 可以从 Git 代码仓库(如 GitHub 和 GitLab)提取包。
范围注册表 You can set up a package registry server to host your package and then publish it to that registry using the npm publish command. Your package’s consumers can then set up a scoped registry configuration in their project to fetch your custom packages from your own package registry.

Unity Package Manager supports registries based on the npm protocol. Make sure that whatever registry server you choose implements the /-/v1/search or /-/all endpoints.

Warning: When you set up your own package registry server, make sure you use only those features that are compatible with Unity’s Scoped Registries. For example, Unity doesn’t support namespaces using the @scope notation that npm supports.

Most of the time, anonymous access within a local network is adequate to fulfill your security requirements. However, if you want more control over who accesses packages via scoped registries, you can enable npm authentication for specific users. Your package’s customers can then configure their scoped registries to use their npm authentication tokens.


Feature sets