-
Notifications
You must be signed in to change notification settings - Fork 12k
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
18.1.0: Firebase "Class extends value undefined is not a constructor or null" #28038
Comments
@niwolf Can you provide a minimal reproduction for us? Otherwise there's nothing actionable here for us to look into. |
Had the same problem. Looks like the issue is caused by conflicting versions of the pnpm why undici
Legend: production dependency, optional only, dev only
[email protected] ~/workspace/webdocs/test
dependencies:
@angular/fire 18.0.1
├─┬ firebase 10.12.3
│ ├─┬ @firebase/auth 1.7.5
│ │ └── undici 5.28.4
│ ├─┬ @firebase/auth-compat 0.5.10
│ │ ├─┬ @firebase/auth 1.7.5
│ │ │ └── undici 5.28.4
│ │ └── undici 5.28.4
│ ├─┬ @firebase/firestore 4.6.4
│ │ └── undici 5.28.4
│ ├─┬ @firebase/firestore-compat 0.3.33
│ │ └─┬ @firebase/firestore 4.6.4
│ │ └── undici 5.28.4
│ ├─┬ @firebase/functions 0.11.6
│ │ └── undici 5.28.4
│ ├─┬ @firebase/functions-compat 0.3.12
│ │ └─┬ @firebase/functions 0.11.6
│ │ └── undici 5.28.4
│ ├─┬ @firebase/storage 0.12.6
│ │ └── undici 5.28.4
│ └─┬ @firebase/storage-compat 0.3.9
│ └─┬ @firebase/storage 0.12.6
│ └── undici 5.28.4
└─┬ rxfire 6.0.5
└─┬ firebase 10.12.3 peer
└─┬ @firebase/auth 1.7.5
└── undici 5.28.4
devDependencies:
@angular-devkit/build-angular 18.1.0
├─┬ @angular/build 18.1.0
│ └── undici 6.19.2
└── undici 6.19.2 Fix was to simply add an override in "pnpm": {
"overrides" : {
"undici": "6.19.2",
"undici-types": "6.19.2"
}
} Then, after deleting the lockfile and node_modules, and reinstalling packages, everything worked. Hope this helps! |
@thePunderWoman Unfortunately not really, sorry.
I hope this is helping you. |
@clcarter This also seems to work for me. Thank you vm! |
The Angular CLI does not depend on |
This comment was marked as off-topic.
This comment was marked as off-topic.
@alan-agius4 Thanks for your answer. |
AngularFire is managed by the firebase team. |
Alright, got it. Thanks again! |
Closing this since there are no actionable items for us at this time. |
I have the exact same problem. I have setup a new web app project in Visual Code and did not change any code at all. Everything works fine. then I add @angular/fire and the first error I got was No overload matches this call. I commented out the locationID line but then I got 0:48:08 [vite] Error when evaluating SSR module /@fs/C:/Users/HP ProDesk i5/angularWorkspace/web-app/.angular/cache/18.1.1/vite/deps_ssr/chunk-UEELBQ5E.js?v=9fb4ba3a: 10:48:08 [vite] Error when evaluating SSR module /@fs/C:/Users/HP ProDesk i5/angularWorkspace/web-app/.angular/cache/18.1.1/vite/deps_ssr/@angular_fire_firestore.js?v=9fb4ba3a: I I decided to check things out and the app runs fine if I comment out |
@clcarter |
pnpm is a package management system, like yarn or npm itself. Here in the package.json file, For yarn you would either use the "resolutions": {
"undici": "6.19.2",
"undici-types": "6.19.2"
} For npm, as of version 8.3, you can use the top-level "overrides" : {
"undici": "6.19.2",
"undici-types": "6.19.2"
} reference: https://stackoverflow.com/questions/52416312/npm-equivalent-of-yarn-resolutions |
thx @clcarter works. I hope the angularFire team and implement a proper fix for this but. So far so good. :) |
Thanks @clcarter . That helped! ❤️ |
@JGSolutions and @AhsanAyaz if no body raise the issue on angular/fire repo I doubt that it will be fixed ... |
Sad! |
@clcarter works, thanks. |
BTW disabling angular cache |
@clcarter using
while make
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
Yes
Description
After updating to version 18.1.0. I am getting the following error on
ng-serve
:Please provide a link to a minimal reproduction of the bug
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: