[Snyk] Fix for 1 vulnerabilities

[macroscope-cloud]

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

Snyk changed the following file(s):

• examples/Portico/google-pay/package.json
• examples/Portico/google-pay/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Uncaught Exception SNYK-JS-QS-19432019	738

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

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:

🦉 Uncaught Exception

[macroscope-cloud]

This update includes major version upgrades for both express and body-parser, introducing significant breaking changes that require code modifications and thorough testing.

express@4.22.0 → express@5.1.0 (High Risk)

The upgrade to Express 5 is a major update with numerous breaking changes. An official codemod tool is available to help automate parts of the migration: npx @expressjs/codemod upgrade.

Key Breaking Changes:

• Node.js Requirement: Support for Node.js versions below 18 has been dropped.
• Asynchronous Error Handling: Express 5 now automatically catches errors from rejected promises in async middleware, which may change existing error handling logic. Manual try/catch blocks for this purpose should be removed.
• Routing and Path Matching:
  • The use of regular expressions directly in route paths is no longer supported to mitigate ReDoS vulnerabilities.
  • The syntax for optional parameters and wildcards has changed (e.g., :name? becomes {:name}).
  • The req.param() method has been removed. You must now use req.params, req.body, or req.query directly.
• Removed/Changed Methods:
  • Deprecated method signatures like res.send(status, body) are removed. Use the chained res.status(status).send(body) instead.
  • app.del() has been removed; use app.delete().
  • The special 'back' string for res.redirect() is no longer supported.

body-parser@1.20.4 → body-parser@2.1.0 (High Risk)

This is a major version upgrade with several breaking changes.

Key Breaking Changes:

• Node.js Requirement: The minimum supported Node.js version is now 18.
• req.body Behavior: The req.body object is no longer initialized to an empty object ({}) if no body is parsed. It will be undefined, which can break logic that assumes an empty object.
• Middleware Removal: The generic bodyParser() combination middleware has been removed. You must use specific parsers like bodyParser.json() or bodyParser.urlencoded().
• urlencoded.extended Default: The extended option for the urlencoded parser now defaults to false. If your application relies on parsing nested objects, you must explicitly set extended: true.

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