-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[6.0.2] Invalid constructor parameter decorator Error: getInternalNameOfClass() called on a non-ES5 class: expected AngularFireModule to have an inner class declaration #2521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Same problem here
But also with older versions in Angular 9 |
Same error with I get this with a standard AngularFire 6.0.1 works fine. |
I can confirm, version 6.0.1 is working fine, but not 6.0.2. |
I also had the same error with AngularFire 6.0.0 worked for me. |
Any info when this will be fixed. I have same problem. |
Change compilerOptions in tsconfig.json file from es5 to es2015, |
@kagisoW same error Compiling @angular/fire : module as esm5 chunk {main} main.js, main.js.map (main) 2.07 kB [initial] [rendered] WARNING in Invalid constructor parameter decorator in {[project directory]}/node_modules/@angular/fire/fesm2015/angular-fire.js: ERROR in getInternalNameOfClass() called on a non-ES5 class: expected AngularFireModule to have an inner class declaration |
after migrating from angular8 to angular10, passing through angular9 I also have this type of error at least with an app:
errors: Warning: Invalid constructor parameter decorator in /home/andrea/lavoro/angular/Angular-Animations-Owl-Carousel-Demo/node_modules/angular-font-awesome/dist/angular-font-awesome.js: |
I solved removing all references and node_modules of angular-font-awesome, now I', using @fortawesome/angular-fontawesome 0.7.0 |
It is maybe the solution, I added the following
and have es2015 in {
"compilerOptions": {
...
"target": "es2015",
"module": "esnext",
"lib": [
"es2019",
"dom"
],
...
} and I got Angular 10 now and seems everything is fine. |
Seems to have work-around, closing. |
Yes. By disabling compatibility with old browsers. |
I resolve a similar issue by running |
Version info
Angular: latest 9.x (9.1.11)
Firebase: latest (7.15.4)
AngularFire: latest (6.0.2)
Other (e.g. Ionic/Cordova, Node, browser, operating system): Ionic project with Cordova
How to reproduce these conditions
Upgrade to 6.0.2
Steps to set up and reproduce
I just moved from 6.0.0 to 6.0.2 and I ran
ng run app:build:production
(actually it is ionic who runs this, I'm runningionic build --prod --engine=browser
I downgraded version to 6.0.0 and the issue has gone!
didn't test 6.0.1.
Debug output
** Errors in the JavaScript console **
The text was updated successfully, but these errors were encountered: