You can specify a dependencyIn the context of the Package Manager, a dependency is a specific package version (expressed in the form package_name@package_version
) that a project or another package requires in order to work. Projects and packages use the dependencies attribute in their manifests to define the set of packages they require. For projects, these are considered direct dependencies; for packages, these are indirect, or transitive, dependencies. More info
See in Glossary as any local folder or tarball that contains a package. This feature is helpful for local offline development and testing.
Note: If you want to reference a package on the local file system as a Git dependency, use the file://<url>
format instead. Unity does not support directly referencing a locally-accessible Git repository with a file path. For more information on the file://<url>
format, see Git dependenciesThe Package Manager retrieves Git dependencies from a Git repository directly rather than from a package registry. Git dependencies use a Git URL reference instead of a version, and there’s no guarantee about the package quality, stability, validity, or even whether the version stated in its package.json
file respects Semantic Versioning rules with regards to officially published releases of this package. More info
See in Glossary.
This section describes how to use 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 to set up a local dependency. If you want to use the Package Manager window instead, follow the instructions on these pages:
The path reference always begins with the file:
prefix, and uses forward slashes (/
) for path separators.
Note: On Windows, you can also use backslashes (\
), but only if you escape each one (for example, "file:..\\github\\my_package_folder"
or "file:C:\\Users\\my_username\\github\\my_package_folder"
). These paths are not as easy to read as the forward slashes, they are prone to typing errors, and you can’t use them anywhere but on a Windows machine. For these reasons, using forward slashes is preferable.
You can use either absolute paths, or paths that are relative to the project’s Packages
folder (that is, the root folder of the project manifest). In other words, a path preceded with two dots (..
) refers to the root of the project path, so that ../another_folder
is a sibling of the Packages
folder.
Tip: Relative paths with forward-slashes provide better portability across different machines and operating systems when tracking a project and packages in the same repository.
For Windows absolute paths, the drive letter and its colon (usually C:
) follows the file:
prefix but is otherwise identical to Linux or macOS paths.
After the file:
prefix, the path is a standard relative path:
{
"dependencies": {
"my_package_a": "file:../github/my_package_folder",
"my_package_b": "file:../Downloads/my_package_tarball.tgz"
}
}
After the file:
prefix, the path is a standard POSIX path, starting with a forward slash /
:
{
"dependencies": {
"my_package_a": "file:/Users/my_username/github/my_package_folder",
"my_package_b": "file:/Users/my_username/Downloads/my_package_tarball.tgz"
}
}
Notice that the drive letter immediately follows the file:
prefix:
{
"dependencies": {
"my_package_a": "file:C:/Users/my_username/github/my_package_folder",
"my_package_b": "file:C:/Users/my_username/Downloads/my_package_tarball.tgz"
}
}
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising. Some 3rd party video providers do not allow video views without targeting cookies. If you are experiencing difficulty viewing a video, you will need to set your cookie preferences for targeting to yes if you wish to view videos from these providers. Unity does not control this.
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.