Closed rodrigoehlers closed 3 years ago
Yeah, we need to remove peerDependencies from pkg json and use patch-package to patch manypkg so that it doesn't use peerDeps.
Same problem here on Windows, Node v15.11.0. With the suggestion --legacy-peer-deps
it works.
What is the problem?
When running
npm i -g blitz
on Node.js version 14.16.0 with npm version 7.6.1, the install fails with the following error output.If re-trying with
--legacy-peer-deps
as suggested, it works.This could have something to do with the way peer dependencies are handled in the new npm major version 7.y.z+.
What are detailed steps to reproduce this?
See section "What is the problem?".
Run
blitz -v
and paste the output here:After installing with
--legacy-peer-deps
and deliberately not running in a blitz project folder.Notice blitz version being printed as
0.30.6
though runningnpm list -g --depth=0
prints the following.