Background
tsconfig.json currently uses moduleResolution: "node" (the legacy Node 10 strategy) with ignoreDeprecations: "5.0" to suppress the TypeScript deprecation warning.
The reason we cannot switch to "bundler" yet: rxfire uses subpath exports (e.g. rxfire/firestore, rxfire/auth), and the "bundler" resolution mode does not resolve these correctly with the current build setup.
Goal
Switch moduleResolution from "node" to "bundler" (or "node16" / "nodenext") and remove ignoreDeprecations.
Investigation needed
- Determine whether rxfire subpath import issues are a config problem (vite.config.ts / tsconfig paths) or a gap in rxfire's package.json exports map
- Check if rxfire has updated its exports map to be compatible with non-legacy resolution
- Evaluate
"node16" as an intermediate step if "bundler" is not viable
Background
tsconfig.jsoncurrently usesmoduleResolution: "node"(the legacy Node 10 strategy) withignoreDeprecations: "5.0"to suppress the TypeScript deprecation warning.The reason we cannot switch to
"bundler"yet: rxfire uses subpath exports (e.g.rxfire/firestore,rxfire/auth), and the"bundler"resolution mode does not resolve these correctly with the current build setup.Goal
Switch
moduleResolutionfrom"node"to"bundler"(or"node16"/"nodenext") and removeignoreDeprecations.Investigation needed
"node16"as an intermediate step if"bundler"is not viable