-
Notifications
You must be signed in to change notification settings - Fork 175
Open
Description
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
- Clone the repository.
- Notice the presence of the
yarn.lockfile. - 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.lockfile and update the documentation accordingly. - If Yarn is chosen, remove the
package-lock.jsonfile (if it exists) and update the documentation to instruct users to runyarn 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.
Metadata
Metadata
Assignees
Labels
No labels