[Snyk] Fix for 1 vulnerabilities

[cdobru]

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
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-14724253	710

---

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

[cdobru]

⛔ Snyk checks have failed. 13 issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (13)
⛔	Open Source Security	0	5	8	0	13 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[cdobru]

⛔ Snyk checks have failed. 13 issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (13)
⛔	Open Source Security	0	5	8	0	13 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[cdobru]

This upgrade introduces a significant change in how request bodies are parsed. As of Express v4.16.0, the body-parser middleware is now included by default, making the separate body-parser package redundant for most use cases.

Source: Express.js documentation
Recommendation: It is highly recommended to remove the body-parser dependency and update your application to use the native Express methods (express.json() and express.urlencoded()) to avoid maintaining a redundant package.

Highlights:

• Replace body-parser middleware: Change app.use(bodyParser.json()) to app.use(express.json()).
• Remove dependency: Uninstall body-parser from your package.json as its functionality is now built into Express.

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

[cdobru]

This upgrade introduces a significant breaking change in how request bodies are parsed. The body-parser dependency is no longer required for most use cases, as its functionality is now built into Express itself.

Highlights:

• Replace body-parser middleware: Since Express v4.16.0, express.json() and express.urlencoded() are included. You should replace app.use(bodyParser.json()) with app.use(express.json()).
• Remove body-parser dependency: After updating the code to use the native Express methods, the body-parser package can be removed from your project's dependencies.

Source: Express documentation, body-parser documentation
Recommendation: Update middleware initialization to use the native express.json() and express.urlencoded() methods, then remove the body-parser package and merge.

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

[cdobru]

This upgrade introduces a significant change in how request bodies are parsed. The body-parser package is now deprecated and its functionality is integrated directly into Express. You must replace the standalone body-parser middleware with the built-in express.json() and express.urlencoded() middleware.

Highlights:

• Remove body-parser dependency: The package is no longer needed as of Express 4.16.0.
• Update middleware usage: Replace app.use(bodyParser.json()) with app.use(express.json()) and app.use(bodyParser.urlencoded(...)) with app.use(express.urlencoded(...)).

Source: Express documentation, body-parser documentation
Recommendation: Remove the body-parser package and update your application's middleware initialization to use the native Express methods before merging.

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

[cdobru]

This upgrade carries a high risk due to a significant breaking change in body-parser that could lead to silent data loss. The express upgrade is low-risk.

**Breaking Change Assessment: body-parser@1.9.0 → 1.20.4

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

[cdobru]

This upgrade introduces a significant breaking change related to how request bodies are parsed. The standalone body-parser package is deprecated and its functionality has been integrated directly into Express as of version 4.16.0. This requires a code change to remove the dependency and use the new built-in middleware.

Highlights:

• Remove body-parser dependency: The package is no longer needed when using modern versions of Express.
• Replace middleware usage: Update app.use(bodyParser.json()) to app.use(express.json()) and app.use(bodyParser.urlencoded(...)) to app.use(express.urlencoded(...)).

Source: Express.js documentation
Recommendation: Remove the body-parser package and update your application to use the built-in express.json() and express.urlencoded() middleware before merging.

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

[cdobru]

This upgrade to Express v4.22.0 introduces built-in body parsing middleware, making the separate body-parser package redundant and requiring code changes.

Highlights:

• Replace body-parser middleware: Since Express 4.16.0, body-parser's functionality is included by default. You should remove the body-parser dependency.
• Update application code: Replace app.use(bodyParser.json()) with app.use(express.json()) and app.use(bodyParser.urlencoded(...)) with app.use(express.urlencoded(...)).

Source: Express.js documentation
Recommendation: Remove the body-parser package and update middleware initialization to use the native express.json() and express.urlencoded() methods before merging.

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