[Snyk] Security upgrade axios from 0.19.0 to 1.15.0

[appfire-developer]

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.

[appfire-developer]

The upgrade from axios v0.19.0 to v1.15.0 is a major version jump that includes significant breaking changes, primarily introduced in the v1.0.0 release. Direct upgrade without code modification will likely lead to application failures.

Key Breaking Changes:

• Interceptor and Request Configuration: The AxiosRequestConfig interface has been modified. For interceptors, you may need to switch to using InternalAxiosRequestConfig.
• Header Shape Changes: The internal shape and handling of request headers have been altered. Code that directly manipulates the request.headers object may need to be updated.
• ESM Import Syntax: For projects using ESM (e.g., with Vite), the import syntax may have changed. You might need to adjust how you import axios.
• Error Handling: The structure of the error object has been updated. For example, the AxiosError status code type has been fixed, which could affect error handling logic.
• Automatic Content-Type: Axios v1.x has changed its behavior regarding Content-Type for multipart/form-data. It no longer automatically sets the header if another Content-Type is already present.

Recommendation:
This is a high-risk upgrade. Before merging, developers must carefully review their usage of axios, especially interceptors, direct header manipulation, and error handling logic. It is critical to test all API requests thoroughly to ensure compatibility with the new version.

Source: GitHub Discussion on v1.0.0 Migration, axios-1.0.0-migration-guide

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