Error on npm install

[serge1peshcoff]

Describe the bug
npm install fails

To Reproduce
Run `npm install

$ npm i
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint-plugin-promise
npm ERR!   dev eslint-plugin-promise@"^5.1.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint-plugin-promise@"^4.2.1" from [email protected]
npm ERR! node_modules/eslint-config-standard
npm ERR!   dev eslint-config-standard@"^16.0.2" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See <file> for a full report.

Expected behavior
No errors

Desktop (please complete the following information):

• Latest versiion from the development branch

[serge1peshcoff]

I want to rebase #33 to the development branch, as the PR is stale now, but this blocks me so far.

[serge1peshcoff]

@bsrinivas8687 as the person who did the most of the latest commits, can you check this out and also my PR in the comment above? I want it to be merged, as it gets outdated when package-lock.json and yarn.lock are changed.

[bsrinivas8687]

Hi @serge1peshcoff

Can you please try yarn

[serge1peshcoff]

Yarn works, thanks!

[serge1peshcoff]

One more thing: when using yarn, I get this:

warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.

I was confused because of that, if yarn is the only way it is supposed to be done, maybe it's worth to remove a package-lock.json to leave yarn.lock as an only option?

@bsrinivas8687