-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Firestore Lite Does Not Work in Loader #9285
Comments
This doesn't appear to be an issue in Remix. Will it work if you put this logic in a simple Node.js script? This will help us eliminate issues in |
Yes, I have built the same app in NextJS. https://github.com/jdgamble555/nextjs-firebase-todo/blob/master/lib/about.ts The Firestore Teams seems to think this is a Remix problem: J |
This is definitely a remix issue. When I add the
and this error on browser:
While my Firebase debug J |
@jdgamble555
https://github.com/jdgamble555/remix-firebase-test/blob/master/vite.config.ts#L6 same issue: #9324 |
It looks like that fixed it! Shouldn't this be the default? J |
Reproduction
Here is the test repo (need to add any Firebase credentials and query any firebase document):
https://github.com/jdgamble555/remix-firebase-test/blob/master/app/lib/about.server.ts
https://github.com/jdgamble555/remix-firebase-test
The test deployed version (deployed working without Lite):
https://remix-firebase-test.vercel.app/
System Info
Used Package Manager
npm
Expected Behavior
Remix will resolver a firebase document as expected when loading
firebase/firestore
. However, when loading thelite
version, which uses REST API, it will never get resolved.You can test this by changing the path to use Firestore Lite to
firebase/firestore/lite
in thehttps://github.com/jdgamble555/remix-firebase-test/blob/master/app/lib/about.server.ts.
Actual Behavior
It does not get Resolved. I submitted a bug report to Firebase. Firebase says this is a Remix problem.
firebase/firebase-js-sdk#8195
Also probably related to:
firebase/firebase-js-sdk#7911
J
The text was updated successfully, but these errors were encountered: