[Snyk] Security upgrade axios from 0.26.0 to 1.15.0

[dhcrees]

Snyk has created this PR to fix 2 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
	Unintended Proxy or Intermediary ('Confused Deputy') SNYK-JS-AXIOS-15965856	848
	HTTP Response Splitting SNYK-JS-AXIOS-15969258	636

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[dhcrees]

The upgrade of axios from v0.26.0 to v1.15.0 is a major version change that introduces several significant breaking changes requiring code modifications.

Key Breaking Changes:

• ESM Import Syntax: The import statement has changed from a named import to a default import. You must update import { axios } from 'axios' to import axios from 'axios'.
• Request Headers: The common object has been removed from request.headers. Code that accessed headers via request.headers.common.HeaderName must be changed to access them directly, like request.headers.HeaderName.
• Interceptor config Type: When using TypeScript, the config parameter in request interceptors now requires the InternalAxiosRequestConfig type if you need to modify it.
• Parameter Serialization: There are numerous breaking changes to how parameters are serialized. You will need to review the latest documentation to ensure your parameter serialization logic is still valid.
• Error Handling: Error handling is now more consistent, with all HTTP error codes resulting in a thrown error.
• Internal Exports: Internals of axios are no longer exported to create a more stable public API. Code relying on internal functions will break.

Source: Upgrade guide, Migration Guide

Recommendation: This upgrade requires careful code review and refactoring. It is highly recommended to follow the official upgrade guide and test thoroughly, paying special attention to interceptors, header manipulation, and parameter serialization.

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