Version: 2021.1
Unity의 패키지 관리자
Package states and lifecycle


이 섹션에서는 Unity 패키지 관리자 기능에 대한 다양한 개념들을 설명합니다.


Multiple versions of each package are available, marking changes to that package along its life cycle. Every time a developer updates the package, they give it a new version number. A change in package version tells you whether it contains a breaking change (major), new backward-compatible functionality (minor), or bug fixes only (patch), following Semantic Versioning.

To view the list of versions available for a specific package, see Finding a specific version.


매니페스트 파일에는 다음의 두 가지 타입이 있습니다.

  • Project manifests (manifest.json) store information that the Package Manager needs to locate and load the right packages, including a list of packages and versions declared as dependencies.
  • Package manifests (package.json) store information about a specific package, and a list of packages and versions that the package requires.

두 파일 모두 JSON(JavaScript Object Notation) 구문을 사용합니다.


In the domain of Unity’s Package Manager, a package registry is a server that stores package contents and information (metadata) on each package version. Unity maintains a central registry of official packages that are available for distribution. By default, all projects use the official Unity package registry, but you can add additional registries to store and distribute private packages or stage custom packages while you are developing them.

패키지 관리

Unity 패키지 관리자는 전체 패키지 시스템을 관리하는 툴입니다. 주로 수행하는 작업은 다음과 같습니다.

The Unity Package Manager installs samples, tools, and assets on a per-project basis, rather than installing them across all projects for a specific machine or device. It uses a global cache to store downloaded package metadata and contents. Once installed in a project, Unity treats package assets just like any other asset in the project, except that these assets are stored inside the package folder and are immutable. You can only permanently change content from Local and Embedded package sources.

패키지 소스

소스는 패키지의 출처를 설명합니다.

소스 설명
레지스트리 The Unity Package Manager downloads most packages from a package registry server into a global cache on your computer as you request them. These packages are immutable, so you can use them in your project, but you cannot modify them or change their package manifests.
Built-in These packages allow you to enable or disable Unity features (for example, Terrain Physics, Animation, etc.). They are immutable. For more information, see Built-in packages.
Embedded Any package stored inside your project folder is embedded. This source corresponds with the Custom state because you typically put all the scripts, libraries, samples, and other assets your new package needs in a folder under your project folder when you begin development on a custom package.
Local You can install a package from any folder on your computer (for example, if you have cloned a development repository locally).
Tarball (local) You can install a package from a tarball file on your computer. The Package Manager extracts the package from the tarball and stores it in the cache. However, these packages are immutable, unlike installations from a local folder.
Git The Package Manager installs Git-based packages directly from a Git repository instead of from the package registry server.

패키지에 대한 패키지 매니페스트를 편집하려면 패키지 검사를 참조하십시오.

The Package Manager window displays a tag that corresponds to some of these sources. For more information, see Tags.

Unity의 패키지 관리자
Package states and lifecycle