Dependencies

The dependencies attribute in the project manifestEach Unity Project has a Project manifest, which acts as an entry point for the Package Manager. This file must be available in the <project>/Packages directory. The Package Manager uses it to configure many things, including a list of dependencies for that Project, as well as any package repository to query for packages. More info
See in Glossary is a JSON object that maps a package name to a version. The version number indicates which version of the package to download from the package registry. For example:

{
  "dependencies": {
    "com.my-package": "2.3.1",
    "com.my-other-package": "1.0.1-preview.1",
       etc.
  }
}

In addition to using version numbers, the Package Manager also supports adding project dependencies with the following:

• Embedded dependencies
• Local paths
• Git URLs

Direct and indirect dependencies

A direct dependency is a project-level dependency. When you install a package through the Package Manager window, or manually edit the project manifest.json file to explicitly add a dependency, you are creating a direct package dependency ():

Packages can declare their own dependencies to other packages. Such package dependencies become indirect (), or transitive, dependencies of your project when you install the package.

The Package Manager determines which version of each package to install, no matter how it becomes a dependency of your project. To do this, it prioritizes direct dependencies over indirect dependencies, as long as the higher priority version doesn’t violate any other requirements.

This evaluation is called dependency resolution, and roughly follows this logic:

1. Select the version of the direct dependency.
2. If there is no direct dependency and this is a built-in packageBuilt-in packages allow users to toggle Unity features on or off through the Package Manager. Enabling or disabling a package reduces the run-time build size. For example, most Projects don’t use the legacy Particle System. By removing the abstracted package of this feature, the related code and resources are not part of the final built product. Typically, these packages contain only the package manifest and are bundled with Unity (rather than available on the package registry).
   See in Glossary version, select the built-in version.
3. If there is no direct dependency and this is not a built-in version, check whether this is an indirect dependency of more than one package:
   • If this is an indirect dependency of only one package in the project, there is no conflict, so select the higher of these versions:
     • This indirect dependency’s version
     • The minimum version required by Unity
   • If multiple indirect dependencies occur, that might create a conflict if the indirect dependencies request more than one version. The Package Manager can resolve most conflicts with an automatic conflict resolution strategy.

In any case, you can manually override these resolution strategies. To do this, request a specific version in the project manifest (either by installing from the Package Manager window or by editing the manifest directly). This creates a direct dependency, which takes precedence over any resolution strategy.