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.
it's a problem with peer dependencies in the latest version of npm (v7) which is still a beta version.
0 comments