firebaseui/ng-bootstrap

@angular/fire v6 compatibility

maikelnight1234 opened this issue · 4 comments

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ X ] feature request

OS and Version?

Windows 10

Versions

 _                      _                 ____ _     ___
/ \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|

/ △ \ | '_ \ / | | | | |/ _ | '__| | | | | | |
/ ___ | | | | (
| | || | | (| | | | || | | |
// __| ||_, |_,||_,|| _|||
|___/

Angular CLI: 9.0.4
Node: 12.16.1
OS: win32 x64

Angular: 9.0.4
... animations, cli, core, forms
Ivy Workspace: Yes

Package Version

@angular-devkit/architect 0.900.3
@angular-devkit/build-angular 0.900.3
@angular-devkit/build-optimizer 0.900.3
@angular-devkit/build-webpack 0.900.3
@angular-devkit/core 9.0.3
@angular-devkit/schematics 9.0.4
@angular/cdk 9.1.0
@angular/common 9.0.3
@angular/compiler 9.0.3
@angular/compiler-cli 9.0.3
@angular/fire 6.0.0-rc.1
@angular/flex-layout 9.0.0-beta.29
@angular/language-service 9.0.3
@angular/material 9.1.0
@angular/platform-browser 9.0.3
@angular/platform-browser-dynamic 9.0.3
@angular/router 9.0.3
@ngtools/webpack 9.0.3
@schematics/angular 9.0.4
@schematics/update 0.900.4
rxjs 6.5.4
typescript 3.7.5
webpack 4.41.2

Repro steps

  1. Install and configure ng-bootstrap in my Angular project
  2. ng serve

The log given by the failure

ERROR in ./node_modules/@firebaseui/ng-bootstrap/ivy_ngcc/esm2015/ng-bootstrap.js 1614:29-54
"export 'FirebaseNameOrConfigToken' was not found in '@angular/fire'
ERROR in ./node_modules/@firebaseui/ng-bootstrap/ivy_ngcc/esm2015/ng-bootstrap.js 1610:29-49
"export 'FirebaseOptionsToken' was not found in '@angular/fire'

Desired functionality

Compile and serve the UI.

Mention any other details that might be useful

I had the same error with ngx-auth-firebaseui. The problem seems to be with @angular/fire v6.

Thanks!

Same issue for me! did you get it runing?

still not working as of today, anyone figured out how to make it work?

Anyone have a workaround for this?

I got it working by turning off ivy:

tsconfig.json

"angularCompilerOptions": {
"enableIvy": false,