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.
[V5 update for #18990]
What does it do?
upgrade
Don't do anything and display the helpupgrade major
Will try upgrading to the next available major (only if the project is already on the latest minor.patch version for the current major), if none is found, it'll abortupgrade minor
todo in another PRupgrade patch
todo in another PRupgrade
packagesrc/cli/commands
contains actual commands' definitions, including the one for the upgradesrc/tasks
directory and is directly called by the upgrade commandsrc/modules/*
types.ts
exports types related to the moduleconstants.ts
exports constants related to the modulexyz.ts
contains domain logic related to the module (usually it exports a factory to create related domain objects. e.g:xyzFactory()
)index.ts
is considered the public module API and only exports what can be used by anyone outside the module__tests__/
directory which contains domain-related testsfs-extra
from10.0.0
to10.1.0
to fix compatibility issues withmemfs
which is used for mockingfs
during tests (see fs-extra's changelog and related issue / fix PR)Why is it needed?
After discussing at length the scope of the upgrade tool internally, we've decided to modify it a bit (mainly related to available commands, options, and how they should behave)
This PR aims to refactor the tool to incorporate those changes while cleaning up the overall architecture.
How to test it?
examples/getstarted
directory, use../../packages/utils/upgrade/bin/upgrade.js <command> [...options]
to test the upgrade CLI