Migrate package manager to backend #2024
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR moves the code that calculates the list of in use packages from the frontend to the backend, allowing backend code to use the information. The data is passed to the fronted via the protocol, and is used to populate the Packages node of the Unity Explorer.
packages-lock.json
if it exists and is up to date. If not, it will read/fall back tomanifest.json
. Thepackages-lock.json
file is created and maintained automatically by Unity, and is not expected to be modified by hand. The user can modifymanifest.json
by hand, and Unity will read this file, resolve packages and updatepackages-lock.json
. If Unity isn't running, the file will get out of date, so up to date packages are read frommanifest.json
Samples~
and docs inDocumentation~
and the IDE ignores*~
by default, meaning these files will not appear in Find in Files or work if opened as a solution.