Skip to content
This repository has been archived by the owner on Dec 1, 2022. It is now read-only.

can't install @nxtend/firebase on a fresh nx 13 workspace #583

Closed
mackelito opened this issue Dec 25, 2021 · 7 comments
Closed

can't install @nxtend/firebase on a fresh nx 13 workspace #583

mackelito opened this issue Dec 25, 2021 · 7 comments

Comments

@mackelito
Copy link

Just trying to install and getting this error..

happy git:(main) ✗ npm install --save-dev --exact @nxtend/firebase                   

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: wehappy@0.0.0
npm ERR! Found: @nrwl/workspace@13.4.1
npm ERR! node_modules/@nrwl/workspace
npm ERR!   dev @nrwl/workspace@"13.4.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @nrwl/workspace@"^12.0.0" from @nxtend/firebase@12.1.0
npm ERR! node_modules/@nxtend/firebase
npm ERR!   dev @nxtend/firebase@"^12.1.0" 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.
@devinshoemaker
Copy link
Collaborator

Can you give me the output of nx report?

@mackelito
Copy link
Author

it worked if adding --legacy-peer-deps..
also to be able to run @nxtend/ionic-angular I first needed to install capacitator using npm install --save-dev --exact @nxtend/capacitor --legacy-peer-deps

nx report:


>  NX  Report complete - copy this into the issue template

  Node : 16.13.0
  OS   : darwin x64
  npm  : 8.1.0
  
  nx : 13.4.1
  @nrwl/angular : 13.4.1
  @nrwl/cli : 13.4.1
  @nrwl/cypress : 13.4.1
  @nrwl/devkit : 13.4.1
  @nrwl/eslint-plugin-nx : 13.4.1
  @nrwl/express : undefined
  @nrwl/jest : 13.4.1
  @nrwl/linter : 13.4.1
  @nrwl/nest : undefined
  @nrwl/next : undefined
  @nrwl/node : undefined
  @nrwl/nx-cloud : 13.0.1
  @nrwl/react : undefined
  @nrwl/react-native : undefined
  @nrwl/schematics : undefined
  @nrwl/tao : 13.4.1
  @nrwl/web : undefined
  @nrwl/workspace : 13.4.1
  @nrwl/storybook : 13.4.1
  @nrwl/gatsby : undefined
  typescript : 4.4.4
  rxjs : 7.4.0
  ---------------------------------------
  Community plugins:
         @angular/animations: 13.1.1
         @angular/cdk: 13.1.1
         @angular/common: 13.1.1
         @angular/compiler: 13.1.1
         @angular/core: 13.1.1
         @angular/fire: 7.2.0
         @angular/forms: 13.1.1
         @angular/material: 13.1.1
         @angular/platform-browser: 13.1.1
         @angular/platform-browser-dynamic: 13.1.1
         @angular/router: 13.1.1
         @angular-devkit/build-angular: 13.1.2
         @angular/cli: 13.1.2
         @angular/compiler-cli: 13.1.1
         @angular/language-service: 13.1.1
         @nxtend/capacitor: 12.1.0
         @nxtend/firebase: 12.1.0
         @nxtend/ionic-angular: 12.1.0

(node:92910) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /Users/markusthiel/Projects/wehappy/node_modules/tslib/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)

@devinshoemaker
Copy link
Collaborator

npm 6+ is a pain with peer dependencies. Nxtend 12 only officially supports Nx 12 as per the peer deps that are required for my plugin, so using --legacy-peer-deps with npm 6+ on an unsupported version of Nx is necessary.

@mackelito
Copy link
Author

Gotcha!... any problems/issue I should expect when using --legacy-peer-deps ?

@devinshoemaker
Copy link
Collaborator

Not really, though I can't plan for compatibility issues with newer Nx versions that my plugins aren't built on. The main difference with npm 6+ is that it installs peer deps when before it assumed they were in your package.json already, and now it abides by the version limits my plugin sets (in my case it's Nx ^12.0.0 which is why it was throwing an error).

@mackelito
Copy link
Author

Roger that.. thx for you help and these awesome plugins!

@pandabuilt
Copy link

Not really, though I can't plan for compatibility issues with newer Nx versions that my plugins aren't built on. .....

Hm... so you're not going to upgrade as NX upgrades?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants