[Snyk] Fix for 2 vulnerabilities

[snyk-io]

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	230
	HTTP Response Splitting SNYK-JS-AXIOS-15969258	186

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.

[snyk-io]

This update includes major version bumps for two packages, introducing significant breaking changes and a high degree of uncertainty.

Top 2 Most Impactful Upgrades

• typewriter-effect 7.4.1 → 9.0.0 (HIGH)
• browser-sync 2.27.11 → 3.0.0 (MEDIUM)

---

typewriter-effect (HIGH)

This is a two-major-version upgrade from v7 to v9. No specific changelog or release notes detailing the breaking changes between these versions could be located. Given the significant version jump and the lack of migration documentation, there is a high risk of breaking changes.

Recommendation: Developers must carefully review the package's current documentation to understand the new API and thoroughly test its implementation. It is unknown what has changed between versions 7, 8, and 9.

Source: Package documentation

browser-sync (MEDIUM)

The upgrade to version 3.0.0 introduces a key breaking change and likely drops support for older Node.js versions.

• Breaking Change: The localtunnel feature has been removed. This was an optional feature, but if your application relied on it, you will need to find an alternative.
• Environment: While not explicitly stated in the main changelog, related packages have noted that browser-sync v3 requires a more modern Node.js environment (likely Node 18+). Support for Node.js 16 and older may have been dropped.

Recommendation: Verify if your project uses the localtunnel feature. Confirm that your deployment environment meets the new, unstated Node.js version requirements.

Source: GitHub Releases

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

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

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