Upgrade Dependencies to Resolve Deprecations, Conflicts, and Security Vulnerabilities

[julioest]

Overview

Our project is facing npm deprecation warnings, dependency conflicts, and security vulnerabilities. Resolving these issues is essential for maintaining stability, security, and long-term maintainability.

Issues Identified

Deprecation Warnings

• [email protected]: Replace with URLSearchParams.
• [email protected]: Upgrade to [email protected].
• [email protected]: Upgrade to [email protected].
• Additional Deprecated Packages: Includes urix, stable, uuid, and more.

Dependency Conflicts

• Example: Conflicts between [email protected] and @typescript-eslint/[email protected].
• Impact: May cause unexpected behavior or build failures.

Security Vulnerabilities

• Summary:
  • Low: 5
  • Moderate: 61
  • High: 35
  • Critical: 1
• Recommendations:
  • Run npm audit fix for non-breaking fixes.
  • Use npm audit fix --force with caution for breaking changes.
  • Manually resolve remaining issues.

Proposed Actions

Upgrade Deprecated Dependencies

• Replace querystring with URLSearchParams.
• Upgrade to [email protected] and [email protected].
• Update other deprecated packages as necessary.

Resolve Dependency Conflicts

• Align @typescript-eslint/parser and eslint versions to avoid conflicts.
• Address other dependency issues as identified.

Address Security Vulnerabilities

• Apply automated fixes with npm audit fix.
• Manually update or replace packages with unresolved vulnerabilities.
• Test the application to ensure no regressions.

Acceptance Criteria

• Deprecated packages are upgraded or replaced.
• Conflicts are resolved with compatible dependencies.
• Security vulnerabilities are significantly reduced.
• The project builds and runs without warnings or issues.
• All functionalities are tested and verified.
• Documentation reflects updated dependencies and usage.

Additional Information

https://github.com/boostorg/website-v2-docs/actions/runs/13034378117/job/36361062783?pr=400#step:5:27