norrelop.blogg.se

Is this going to work for you? Probably, yes. So -legacy-peer-deps does not try to install the peerDependencies automatically. The solution is to downgrade angular common or the solution is to use legacy dependencies logic for installing packages using -legacy-peer-deps. So what should be the solution then? The problem is about peer dependencies. This is useful when some 3rd party library is not on NPM, or you want to include some of your projects as modules

OptionalDependencies - these dependencies are optional and failing to install them will not break the installation processīundledDependencies - it’s an array of packages that will come bundled with your package. PeerDependencies - if you set a peer dependency in your package.json, you are telling the person who installs your package that they need that dependency with the specified version (If you want to understand dependencies little bit better, here is very simple site: How npm3 Works) dependencies - these are the essential dependencies that you rely on and call in your project’s codeĭevDependencies - these are your development dependencies, for example, a prettier library for formatting code And the top message says that the angular common found is actually 11.0.3. Here requires angular common 9.1.0 or 10.0.0. Npm ERR! peer || ^10.0.0" from ERR! ERR! from the root projectįirst you should start to read the problem from the bottom to the top. Npm ERR! While resolving: ERR! Found: ERR! ERR! from the root project Here is what I have as error: npm ERR! ERESOLVE unable to resolve dependency tree