When you “remove” a package from your project, the Package Manager is actually removing the project’s direct dependencyA direct dependency occurs when your project “requests” a specific package version. To create a direct dependency, you add that package and version to the dependencies property in your project manifest (expressed in the form
package_name@package_version). More info
See in Glossary from your 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. The result of removing the direct dependency varies, based on the dependencies for the package you are removing:
firstname.lastname@example.org which in turn depends on the
email@example.com, then your project has an direct dependency on Alembic and an indirect dependency on Timeline. More info
Make sure you understand these important notes before you begin:
To remove an installed package:
Open the Package Manager window and select In Project from the PackagesPackages are collections of assets to be shared and re-used in Unity. The Unity Package Manager (UPM) can display, add, and remove packages from your project. These packages are native to the Unity Package Manager and provide a fundamental method of delivering Unity functionality. However, the Unity Package Manager can also display Asset Store packages that you downloaded from the Asset Store. More info
See in Glossary drop-down menu.
Click the Remove button. If this button is:
When the progress bar finishes, the package disappears from the list.
If you want to restore a removed package, follow the instructions for installing a package.
You can only remove packages which are not required by another package or a feature set. The Package Manager enforces this by disabling the Remove button for all required packages.
|A feature set||If a feature set requires the package, it displays a lock icon () both in the list view and in the details view. The details view also displays the name of the feature set that requires the package below the package name in the details view.
However, even if you click the Unlock button, you still can’t remove the package from your project until you remove all feature sets which require it. Unlocking the package lets you request a different version for your project, but it still doesn’t let you remove it.
|Another package||If one or more packages require the selected package, the Remove button is disabled. You can find the name of the package that has the dependency from the Dependencies section of the details view. If you don’t need the other packages, you can remove them and the Package Manager automatically removes this package too.|
Tip: If you don’t see the Dependencies section, follow these instructions to enable the Show Dependencies setting:
Select Advanced Project Settings under the advanced settings icon.
The Package Manager project settingsA broad collection of settings which allow you to configure how Physics, Audio, Networking, Graphics, Input and many other areas of your project behave. More info
See in Glossary window appears.
Under the Advanced Settings group, enable the Show Dependencies option.
Close the Project Settings window. Any packages that are only installed as dependencies in your project now appear in the package list and the detail view now displays a Dependencies section.