J Rob Gant

@Kristinita Unfortunately this does not solve the types issues. If you use an `eslint.config.ts` file instead of `mjs` then `tsc` will report the issues above. However I do really appreciate...

@Kristinita This is not a problem of configuration. This is a problem of incompatible TypeScript types. The problem is the `| undefined` for `meta` (and probably also `rules`) in `index.d.ts`....

The error message I get with the angular project is of the form: > Cannot find module * or its corresponding type declarations. typescript(2307) > There are types at *,...

Thank you, I have opened a ticket there.

Seems like something that should be configurable as there are several code styles.

I suggest these changes to reduce the amount of space that was being taken up: ```js // @ts-check import pluginJs from '@eslint/js'; import preferArrowFunctions from 'eslint-plugin-prefer-arrow-functions'; export default [ pluginJs.configs.recommended,...

@galih9 those messages are an intentional choice made by AngularFire. Angular version has nothing to do with it. They will keep happening until you wrap every AngularFire method in an...

I believe that if you switch from the namespace syntax to the modular style that will solve the issue. https://firebase.google.com/docs/web/modular-upgrade

You could wrap the modular methods in an Angular Service. Still a large change, but mostly just renaming things hopefully. I can describe more if interested. The only other solution...

Something like: ```ts import { EnvironmentInjector, inject, Injectable, runInInjectionContext, } from '@angular/core'; import { doc, Firestore } from '@angular/fire/firestore'; import type { DocumentReference } from '@angular/fire/firestore'; @Injectable({ providedIn: 'root' })...