Title: Inconsistency between yarn.lock file and npm installation instructions

[PaulChass]

Description

There is an inconsistency in the repository regarding the package manager used. The repository contains a yarn.lock file, which suggests that Yarn is being used for dependency management. However, the documentation instructs users to install dependencies using npm install.

Steps to Reproduce

1. Clone the repository.
2. Notice the presence of the yarn.lock file.
3. Refer to the documentation which instructs to run npm install.

Expected Behavior

The repository should consistently use either npm or Yarn for dependency management. The documentation and lock files should reflect the chosen package manager.

Suggested Solution

• Decide on a single package manager for the project.
• If npm is chosen, remove the yarn.lock file and update the documentation accordingly.
• If Yarn is chosen, remove the package-lock.json file (if it exists) and update the documentation to instruct users to run yarn install.

Additional Context

This inconsistency can lead to confusion and potential issues for contributors and users of the project. Standardizing on a single package manager will help maintain consistency and reliability.