[Snyk] Fix for 1 vulnerabilities

[DiogoRDuarte]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-14724253	170

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

[DiogoRDuarte]

This release contains major breaking changes for both npm and npmi. The npm upgrade to v7.0.0 introduces a new lockfile format and now installs peerDependencies by default, which can break existing builds. The npmi upgrade to v4.0.0 no longer bundles npm as a dependency, instead relying on a globally installed version.

Top Breaking Changes:

• npm@5.1.0 → npm@7.0.0 (high): This major version upgrade changes core behaviors. The most significant change is that peerDependencies are now installed automatically, which can cause installation to fail if conflicts are found. The package-lock.json format has been updated to v2, and npx has been completely rewritten, which may alter script behaviors.

• npmi@1.0.1 → npmi@4.0.0 (medium): This upgrade fundamentally changes how npmi works. Version 4 no longer includes npm as a dependency and instead uses the globally installed npm. This means the version of npm being executed is no longer controlled by the package, which could lead to inconsistent behavior depending on the environment.

Recommendation: Due to the automatic installation of peerDependencies in npm v7, carefully validate dependency trees for conflicts before merging. For npmi, ensure that all environments have a compatible global version of npm installed. Consider using the --legacy-peer-deps flag with npm v7 as a temporary workaround to mimic the old behavior if immediate migration is not possible.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.