Update Frontend Dependancies

[nilsstreedain]

Update Frontend Dependencies

User Story Statement

"As a Frontend Developer, I want to update the frontend dependencies of our project, so that we can ensure the application is running on the most stable, secure, and efficient libraries and frameworks."

Background

Why do we want it?

• To address known security vulnerabilities in current dependencies.
• To improve performance and compatibility with modern browsers.
• To lay the groundwork for implementing upcoming features that may require newer library versions.

Who is this for?

• Primarily for the development team to streamline future development.
• Indirectly benefits end-users through improved app performance and security.

Do we have data to support it?

• GitHub Dependabot security audit reports highlight vulnerabilities in current dependencies.

Solution/Requirements

Functional

• Update all frontend libraries to their latest stable versions.
• Ensure no breaking changes affect existing functionality.
• Perform thorough testing to confirm compatibility.

Non-Functional

• Maintain or improve current application performance.
• Ensure updated dependencies do not introduce new security vulnerabilities.

Design resources:

• N/A (This task is not design-focused).

Dependencies

Blocked By:

• No, this task is independent.

Blocking:

• Not directly, new features may be improved by updating dependencies.

Tasks and Subtasks

N/A

Estimate

Approximately 1 week, considering potential issues that might arise during testing.

Open Questions

N/A

Acceptance Criteria

• All frontend dependencies are updated to their latest stable versions.
• The application runs without errors and passes all existing tests.
• New changes are documented and communicated to the team.

Definition of Done

• The updates are reviewed and approved by another developer.
• Integration with the main branch is complete and all CI/CD pipelines pass.
• A final check is conducted to ensure compatibility with all major browsers and devices.