You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gh repo clone angular/angularfire
cd .\angularfire\samples\compat\
npm install // fails
npm install --legacy-peer-deps (as suggested)
ng serve (does not compile)
Steps to set up and reproduce
Sample data and security rules
n/A
Debug output
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: karma-jasmine-html-reporter@1.7.0
npm ERR! Found: jasmine-core@3.5.0
npm ERR! node_modules/jasmine-core
npm ERR! dev jasmine-core@"~3.5.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer jasmine-core@">=3.8" from karma-jasmine-html-reporter@1.7.0
npm ERR! node_modules/karma-jasmine-html-reporter
npm ERR! dev karma-jasmine-html-reporter@"^1.5.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: jasmine-core@5.1.2
npm ERR! node_modules/jasmine-core
npm ERR! peer jasmine-core@">=3.8" from karma-jasmine-html-reporter@1.7.0
npm ERR! node_modules/karma-jasmine-html-reporter
npm ERR! dev karma-jasmine-html-reporter@"^1.5.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.
npm ERR!
npm ERR!
npm ERR! For a full report see:
Expected behavior
should compile
Actual behavior
does not compile
The text was updated successfully, but these errors were encountered:
Version info
node -v
v20.11.1
How to reproduce these conditions
gh repo clone angular/angularfire
cd .\angularfire\samples\compat\
npm install // fails
npm install --legacy-peer-deps (as suggested)
ng serve (does not compile)
Steps to set up and reproduce
Sample data and security rules
n/A
Debug output
Expected behavior
should compile
Actual behavior
does not compile
The text was updated successfully, but these errors were encountered: