Skip to content

fix: engine-strict issue on npm install - #148

Open
kchindam-infy wants to merge 1 commit into
npm:mainfrom
kchindam-infy:kc/fix-engine-strict-issue
Open

fix: engine-strict issue on npm install#148
kchindam-infy wants to merge 1 commit into
npm:mainfrom
kchindam-infy:kc/fix-engine-strict-issue

Conversation

@kchindam-infy

Copy link
Copy Markdown

The fix addresses an issue where the engine-strict flag is not enforced during the version resolution phase in npm. When engine-strict is enabled, npm should only install package versions that are compatible with the current Node.js version, as specified in the package's engines field. However, prior to this fix, npm did not consider the engines.node field during version resolution, potentially leading to the installation of incompatible package versions.

We introduced the engineStrict option in the pickManifest function to control the engine compatibility enforcement. When engineStrict is enabled, the function will only consider package versions that are compatible with the current Node.js version.

References

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant