AngularFire 7.2 doesn't compile with latest Angular 13.1 and Typescript 4.5
See original GitHub issueUpdate Angular & Typescript to latest (13.1.0 and 4.5.3) => ng serve
errors in the terminal:
Error: node_modules/@angular/fire/compat/proxy.d.ts:7:49 - error TS2344: Type ‘T[K]’ does not satisfy the constraint ‘(…args: any) => any’.
Caused by this file: https://github.com/angular/angularfire/blob/master/src/compat/proxy.ts Latest version of Typescript (4.5.3) doesn’t like T[K].
Issue Analytics
- State:
- Created 2 years ago
- Reactions:18
- Comments:21 (2 by maintainers)
Top Results From Across the Web
Angular Fire Module Init Error raise on Proxy - Stack Overflow
Type 'T[PromiseReturningFunctionPropertyNames<T>]' is not assignable to type '(...args: any) => any'. Type 'T[ReturnType<T[FunctionPropertyNames ...
Read more >angular/fire - npm
The official Angular library for Firebase.. Latest version: 7.5.0, last published: a month ago. Start using @angular/fire in your project by ...
Read more >npm err eresolve could not resolve angular - You.com
As of now, the documentation for angular fire is not up to date. ... Q&A for work. ... <error> @schematics/angular 13.2.5 rxjs 6.6.7...
Read more >How to update local Angular CLI version? in package.json file ...
One I faced when I installed the latest version of Angular Material with version ~8.1.1 and my Angular core was still ~7.2.0 in...
Read more >Firebase JavaScript SDK Release Notes - Google
This allows the SDK to work with the upcoming framework-aware Firebase tools (currently an experimental release) ... This includes apps using Angular 13.1+....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Set
skipLibCheck: true
in your tsconfig for now.A temporary fix for this is to revert typescript back to 4.4.4:
npm install typescript@4.4.4