종속성 및 해결

When you work in the Package Manager window, you can install a package from several sources (a registry, a local folder or tarball, a Git URL, and by name). However, while the Package Manager installs packages from these sources seamlessly, it first has to make a series of calculations to decide which version to install. It also has to decide which other packages and versions to install to support the package you selected.

직접 종속성

Package Manager 창을 통해 설치할 패키지 버전을 선택하면 프로젝트 매니페스트에 “종속성”을 추가하게 됩니다.프로젝트가 작동하기 위해 특정 패키지의 특정 버전이 필요하다는 선언입니다.프로젝트에 종속성을 추가하려면 <project-root>/Packages/manifest.json 파일의 dependencies 프로퍼티에 package-name@package-version 형식의 패키지 및 버전에 대한 레퍼런스를 추가하십시오.프로젝트가 직접 종속되어 있으므로 이를 “직접” 종속성이라고 합니다.

간접 종속성

Packages can also require other packages to work. These are called “indirect” (or transitive) dependencies. The package developer adds these to the dependencies property of the package manifest file during development (<package-root>/package.json). For example, in the diagram below, the alembic@1.0.7 package has a dependency on the timeline@1.0.0 package, so the timeline package is an “indirect” dependency. Conversely, the project has dependencies on the cinemachine@2.6.0 and alembic@1.0.7 packages, so those are both “direct” dependencies.

버전 오버라이드

When you add a package version as a dependency, that version isn’t necessarily the version that the Package Manager installs. The reason is because the Package Manager has to consider all dependencies in your project, whether direct or indirect. In the following example, the XR Plugin Management package requested was version 4.0.3. However, the Package Manager installed version 4.0.6 because another package depended on the higher version, as indicated in the information message (B):

종속성 그래프

The Package Manager can install only one package version at a time, so it has to construct a dependency graph. This graph is a list of every direct and indirect dependency for the project. The dependency graph determines which version of each package to install.

잠금 파일

When the Package Manager resolves all version conflicts, it saves the resolution in a lock file for two reasons:

• Determinism, to make sure that the same packages are reliably installed every time.
• Efficiency, to reduce the amount of time and resources it takes to compute the dependency graph again.