fix: Rename npm_package_json to npm_requirements #621
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.
Description
This change was missed in #293. Documentation is up to date, code is not.
Fixes #506
Replace #507
Motivation and Context
This would solve inconsistencies in the documentation. It says the field is named
npm_requirements
, but it's in factnpm_package_json
.Breaking Changes
There is no breaking change. The wrongly documented field
npm_requirements
will start to work as expected. The previous non-documented fieldnpm_package_json
will keep working.How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request