The packages are loaded into a separate folder structure, not the project assets folder, so they do not get rolled into the version management system for the project, thus making package version management and updates a lot easier. It is a “proper” package management system based on NPM and has all of the dependency management that you would expect. Unity Package Manager (UPM) is a more recent development than asset packages. This is particularly a problem for code-based assets, making independent version control for the package code almost impossible. However, it does not include any concept of dependencies and since the assets are imported into the project file structure itself they then become part of the version control of the project making package version control much more difficult. It works well for sets of icons, UIs, and template projects. The value of this format is that it is easy to create and easy to use.

This is the package format used by the Unity Asset Store. When imported, the assets are imported into the asset folder system for the project. The bundle is easy to distribute as a single file and is relatively easy to import into the project using a single command. Unity Asset Packages are bundles of Unity assets compressed into a. There are also a couple of types of package management that are not available out of the box: There are two types of Unity package management provided out of the box: I am not going to provide much introduction to Unity, since if you do not know what it is then this article is probably not of much interest.īut in case you are interested, the least you need to know is that Unity is a development environment and compiler for Virtual Reality applications and consumes a number of types of assets such as C# scripts, 3D objects, shaders etc.

Unity package manager