Fix NPM separator warning for negated flags #2930
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.
WHY are these changes introduced?
In #2348 we added a warning when using NPM and passing flags without the separator (
--
).But it turns out that NPM removes the
no_
prefix for the flags. For example, passing--no-release
will result in anpm_config_release
environment variable. So our code to show the warning wasn't working in that case.WHAT is this pull request doing?
Ignore the
no_
prefix from the flags to show the warning in all casesHow to test your changes?
npm run shopify app deploy --no-release -- --path your-app
Measuring impact
How do we know this change was effective? Please choose one:
Checklist
dev
ordeploy
have been reflected in the internal flowchart.