[Feat] Add Support for Custom Package Versions in updateNodePackages Method #414
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 enhances the
updateNodePackages
method in theInstallCommand
class to support custom package versions. This feature allows users to specify custom versions of packages they want to install, providing greater flexibility and control over their project's dependencies.Changes Made
updateNodePackages
Method:$customPackages
to accept an array of custom package versions.package.json
file.Code Changes
Updated
updateNodePackages
MethodExample Usage in
handle
MethodThis enhancement provides more flexibility and control over project dependencies by allowing custom package versions to be specified during the update process. This feature is particularly useful for projects that require specific versions of certain packages.