Add versions info to Project model #4526
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.
Part of #4522
This captures the versions info returned by the launcher into a new
versions
property of theProject
model.The
versions
property stores the version info in the following format:The launcher also reports back
node
andlauncher
versions - which get stored as well.The choice of
current
is for future consideration of storing the node module information in one place - where there may be a difference between thewanted
and thecurrent
version. The choice of key names is based on those used bynpm outdated
output.This PR includes a migration
We also have #4518 open that contains a migration. Depending which one merges first, the other will need to rename its migration file to ensure the ordering is preserved.