Skip to content

[Snyk] Fix for 1 vulnerabilities#529

Open
nglgzz wants to merge 1 commit intomasterfrom
snyk-fix-4dbf8474ca57ce460dbdda13b7f952da
Open

[Snyk] Fix for 1 vulnerabilities#529
nglgzz wants to merge 1 commit intomasterfrom
snyk-fix-4dbf8474ca57ce460dbdda13b7f952da

Conversation

@nglgzz
Copy link
Contributor

@nglgzz nglgzz commented Dec 31, 2025

snyk-top-banner

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

Snyk changed the following file(s):

  • packages/web/package.json
⚠️ Warning
Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity 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

@nglgzz
Copy link
Contributor Author

nglgzz commented Dec 31, 2025

Merge Risk: High

This upgrade to @nestjs/platform-express v11 is a major update that introduces significant breaking changes by adopting Express.js v5 and altering core framework behaviors. The minor update to express itself is not the source of risk; the breaking changes come from NestJS v11's new dependency on Express v5.

Highlights:

  • Routing Syntax Change: NestJS v11 uses Express v5, which changes how route paths are matched. Wildcard routes (*) must now be named parameters (e.g., users/* becomes users/*splat). [1, 8, 13] Applications using wildcard routes will require code modifications.
  • Node.js Requirement: Support for Node.js v12 is dropped. NestJS v10 and higher require at least Node.js v16. [2, 5]

Source: NestJS documentation
Recommendation: Developers must audit all route definitions for the new path syntax and verify Node.js version compatibility before merging this upgrade.

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

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.

2 participants