Closed mellis481 closed 2 years ago
That's due to npm 7 automatically installing peer dependencies. As it is it can be installed using npm install --force
. The newest commit updated the dependencies so that should no longer be necessary, though.
Sounds like we can close this issue thanks to the new commit.
When I pull down the master branch and try to run
npm i
, I get the following error:Not sure why this codebase does not have a
package-lock.json
checked in...