fix: use npm update when building in source #579
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mildaniel
approved these changes
Nov 23, 2023
lucashuy
approved these changes
Nov 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue #, if available:
N/A
Description of changes:
When
--build-in-sourceis used,npm installcommand won't remove any dependency that is removed between 2 invocations.This PR addresses that by adding
NodejsNpmUpdateActionand using it when build-in-source is enabled which runsnpm --no-audit --no-save --unsafe-perm --production --no-package-lock --install-links.--install-linksflag is also removed fromNodejsNpmInstallActionwhich was only used for build in source workflow.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.