angularfire: Current versions of angularfire2 not compatible with the new angular v6 stable release
Version info
Firebase: 4.13.1
AngularFire: 5.0.0-rc.6.0
Debug output
My dry run installation of angular v6 and material/cdk v6
npm WARN angularfire2@5.0.0-rc.7.2-next requires a peer of @angular/common@^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN angularfire2@5.0.0-rc.7.2-next requires a peer of @angular/core@^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN angularfire2@5.0.0-rc.7.2-next requires a peer of @angular/platform-browser@^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN angularfire2@5.0.0-rc.7.2-next requires a peer of @angular/platform-browser-dynamic@^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN angularfire2@5.0.0-rc.7.2-next requires a peer of rxjs@^5.5.4 but none is installed. You must install peer dependencies yourself.
Actual behavior
peerDependencies:
{ '@angular/common': '^5.0.0',
'@angular/core': '^5.0.0',
'@angular/platform-browser': '^5.0.0',
'@angular/platform-browser-dynamic': '^5.0.0',
'@firebase/app': '^0.1.6',
rxjs: '^5.5.4',
'zone.js': '^0.8.0' },
Personal statement
Okay. So I’ve been waiting for the next release of angularfire2 since material2 6.0.0-beta-0. I am stuck at ghillie-soup, cant use new features of 6 beta and up with the current angularfire2 @next and @latest versions.
Please release another version that will make angularfire2 compatible with angular/cdk/material v6.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 13
- Comments: 30 (8 by maintainers)
Commits related to this issue
- test https://github.com/angular/angularfire2/issues/1594 — committed to vincent-cm/angular-starter-test by deleted user 6 years ago
@bluebaroncanada did u install
npm install rxjs@6 rxjs-compat@6 --save
?@lewiswashere RC7 has a fix for that issue. #1574
RC7 Install Command
yarn add angularfire2@5.0.0-rc.7
ornpm install --save angularfire2@5.0.0-rc.7
This is a peer dep warning and it should still work despite the warnings. We will be pushing an update soon.
@cedvdb Yes, we are going to upgrade to rxjs 6 in the near future.
I’m getting a straight error with
ng serve
I get a similar error when trying to install Angularfire2 on a Ionic 3 project.
`npm WARN angularfire2@5.0.0-rc.10 requires a peer of @angular/common@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN angularfire2@5.0.0-rc.10 requires a peer of @angular/core@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN angularfire2@5.0.0-rc.10 requires a peer of @angular/platform-browser@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN angularfire2@5.0.0-rc.10 requires a peer of @angular/platform-browser-dynamic@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN angularfire2@5.0.0-rc.10 requires a peer of rxjs@^6.0.0 but none is installed. You must install peer dependencies yourself.
Ionic 3 still using Angular 5.5 and it’s not recommended to upgrade to 6 until Ionic 4 has ben relesed. Is it safe to use Angularfire2@5.0.0-rc.10 in a Ionic 3/Angular 5.5 project disposing this warnings?
should we run
ng update
for the angularfire2 project 😃I experienced the same issue after running ng update @angular/core, which prevented the operation from running successfully :
@byrondover they’re still using
rxjs-compat
with@angular/fire
@byronglendon using @angular/fire works great with Angular v7
I honestly dont know about peer dep warnings your talking about @davideast until now 😁 I always take per ders seriously.
I have the same issue as @bluebaroncanada and @Sun3
npm install rxjs@6 rxjs-compat@6 --save
replied by @vincent-cm resolved my issue. can now use ng/m2/cdk v6 along with af2. Ill close the issue.@davideast https://github.com/vincent-cm/angular-starter-test This can reproduce
Cannot read property 'OVERWRITE' of undefined
Please run: npm run build:aot and npm run serve:prod to locate the runtime error