Disable npm
configuration parameter engine-strict
when installing dependencies of Jetpack
#5689
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 disables the
engine-strict
parameter in Jetpack's.npmrc
file as we can't ensure that thenode
version used bynpm
to check theengines
parameter is the expected one. The parameter is reverted back after installing the dependencies.NOTE: This change is a temporary workaround until we find a better solution to #5688.
To test:
trunk
branch of the Jetpack repository.npm install
.Additionally, the fix has been also applied to #5687 in order to check that CI jobs succeed 🟢 .
PR submission checklist: