Issue: Dependency Conflict Error During npm install

Description

When attempting to run npm install in the client directory, the following dependency conflict error occurs:

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @typescript-eslint/[email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"^9.3.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/[email protected]
npm error     node_modules/@typescript-eslint/eslint-plugin/node_modules/@typescript-eslint/utils
npm error       @typescript-eslint/utils@"7.10.0" from @typescript-eslint/[email protected]
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         dev @typescript-eslint/eslint-plugin@"^7.10.0" from the root project
npm error       1 more (@typescript-eslint/type-utils)
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   1 more (eslint-plugin-react-refresh)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   dev @typescript-eslint/eslint-plugin@"^7.10.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"^7.10.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/runner/.npm/_logs/2024-07-11T19_17_45_447Z-eresolve-report.txt

npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-07-11T19_17_45_447Z-debug-0.log
Error: Process completed with exit code 1.

Steps to Reproduce

1. Navigate to the client directory.
2. Run npm install.

Expected Behavior

Dependencies should be resolved and installed without errors.

Actual Behavior

An error related to dependency resolution (ERESOLVE) occurs due to conflicting versions of eslint.

Possible Solutions

• Upgrade @typescript-eslint/eslint-plugin: Ensure that you are using the latest compatible version of @typescript-eslint/eslint-plugin which supports the installed version of eslint.

  npm install @typescript-eslint/eslint-plugin@latest

• Downgrade eslint: If upgrading @typescript-eslint/eslint-plugin is not an option, consider downgrading eslint to a compatible version.

  npm install [email protected]

• Use --legacy-peer-deps: As a temporary workaround, you can use the --legacy-peer-deps flag to ignore peer dependency conflicts.

  npm install --legacy-peer-deps

• Force Install: Another temporary workaround is to use the --force flag to forcefully install dependencies.

  npm install --force

Enhancement Request: Lazy Loading & Memoization

Description:

Enhance app performance with two optimizations: Lazy Loading for resources and Memoization for components, boosting speed and user experience.

Lazy Loading for Resources:

Objective:

Integrate lazy loading for non-critical resources (images, scripts) to accelerate initial load times.

Steps:

1. Identify non-critical components/resources.
2. Implement lazy loading using React.lazy, Suspense, and dynamic import.

Memoization for Components:

Objective:

Apply memoization for components to minimize unnecessary re-renders and improve performance.

Steps:

1. Identify components for memoization.
2. Implement memoization using React.memo or equivalent tools.

Expected Benefits:

• Faster initial load times.
• Smoother user interactions.
• Improved overall app performance.

Description:

Transitioning our pet project from the beta stage to a stable release. Tasks include writing tests and conducting code refactoring for improved stability and reliability.

Steps:

1. Assess current codebase.
2. Write essential tests (Vitest, RTL, Cypress).
3. Refactor code for better maintainability.
4. Ensure integration and functionality.
5. Update documentation.