[Snyk] Fix for 1 vulnerabilities

[aluca3]

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

Snyk changed the following file(s):

• package.json
• 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

[aluca3]

This release includes two major version upgrades that introduce significant breaking changes requiring developer action.

Top 3 Most Impactful Upgrades

1. express 4.12.4 → 5.1.0 (high risk): This major upgrade introduces numerous breaking changes that will require code modifications.
2. tap 11.1.5 → 18.0.0 (high risk): This upgrade spans seven major versions, introducing significant changes to the API, CLI, and default behaviors.

Upgrade Details

express 4.12.4 → 5.1.0

This upgrade to a new major version of Express requires significant code and configuration changes. It is not a simple drop-in replacement.

Key Breaking Changes:

• Node.js Requirement: Support for Node.js versions below 18.x has been dropped.
• Promise Support: Express 5 now automatically catches errors from rejected promises in async route handlers, which may change existing error handling logic. Manual try/catch blocks that call next(err) may no longer be necessary.
• Removed Methods: Several deprecated methods have been removed, requiring code updates:
  • app.del() must be replaced with app.delete().
  • The res.send(status, body) signature is removed; use res.status(status).send(body) instead.
  • req.param(name) is removed; use req.params, req.body, or req.query directly.
• Routing Changes: The path matching engine was updated, which changes how route strings are interpreted. Regular expressions in paths are more restricted to mitigate ReDoS vulnerabilities.
• body-parser Integration: The bodyParser() middleware has been removed. req.body is no longer initialized to an empty object by default.

Source: Express 5 Migration Guide, Release Notes

Recommendation: Developers must carefully review the official migration guide and use the provided codemods to automate some of the required changes. Thorough testing is required to ensure routing, error handling, and middleware function as expected.

tap 11.1.5 → 18.0.0

This is a very large version jump for the tap testing framework, crossing seven major versions. It includes a complete rewrite in TypeScript and fundamental changes to configuration and default behavior.

Key Breaking Changes:

• Node.js Requirement: Support for Node.js versions below 10 was dropped in version 15.
• Coverage Enforcement: In version 18, code coverage is enabled and enforced at 100% by default. A test run will fail if coverage is incomplete. This behavior and its configuration flags (--disable-coverage, --allow-incomplete-coverage) are different from previous versions.
• CLI & Configuration: The method for specifying test files has changed from test-regexp to include and exclude glob patterns in .taprc files.
• API Changes:
  • Assertion synonyms like t.is_not_equal() have been removed and are now available in an optional @tapjs/synonyms plugin.
  • Callbacks are no longer supported for t.beforeEach and t.afterEach.
• ESM & TypeScript: Version 18 was rewritten in TypeScript for first-class ESM and CommonJS support, which may affect how tests are written and run.

Source: tap Changelog

Recommendation: This upgrade will likely require significant changes to test scripts, CI configuration, and local development workflows. Developers must review the changelogs for versions 12 through 18, paying special attention to the new coverage defaults and CLI/configuration changes.

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