You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this may be an issue with sveltekit but since this repository represents the blend of sveltekit and firebase it seemed like an appropriate place to document the problem
I have a firebase.ts file configures a connection to firebase. It connects to the emulator if it detects a development environment. This works fine, but if the firebase module is edited while running in development mode / with hot module replacement it results in an error:
Firestore has already been started and its settings can no longer be changed. You can only modify settings before calling any other methods on a Firestore object.
Understood if this ends up being considered irrelevant to this repository, but I thought creating the issue might help others. At this point the only solution I could find is to manually restart npm run dev instead of relying on hot module reloading.
I might not be able to actually tackle this issue with the adapter separate from the Firebase framework. Firebase have added official support for Web Frameworks, so this adapter might end up being deprecated if they add support there.
Describe the Bug
I think this may be an issue with sveltekit but since this repository represents the blend of sveltekit and firebase it seemed like an appropriate place to document the problem
I have a
firebase.ts
file configures a connection to firebase. It connects to the emulator if it detects a development environment. This works fine, but if the firebase module is edited while running in development mode / with hot module replacement it results in an error:Here is the code just for the record:
Steps to Reproduce
npm run dev
Expected Behaviour
I would expect the firestore emulation configuration to continue to work.
svelte-adapter-firebase version
0.14.4
sveltejs/kit version
1.0.0-next.488
The text was updated successfully, but these errors were encountered: