[Bug]: Firebase SSR is not working

[rcannood]

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Current behavior 😯

Note: I'm not sure whether this issue should be posted here or in the vinxi. I will start my posting it here, but if the issue is related to vinxi, I will repost there.

When I deploy an SSR SolidStart application to Firebase, it seems the server returns http status code 500's for very simple requests.

For example, this component does not work when deployed to Firebase, but it does when the PRESET=vercel or PRESET=node-server is used:

import { createResource, createSignal, Match, Switch } from "solid-js";
function fetchServerResource(): Promise<string> {
  "use server";
  return new Promise((resolve) => {
    setTimeout(() => {
      resolve("Hello from the server!");
    }, 1000);
  });
}
export default function SSRLabel() {
  const [data] = createResource<string>(fetchServerResource);
  return (
    <Switch>
      <Match when={data.loading}>Loading...</Match>
      <Match when={data.error}>Error: {data.error}</Match>
      <Match when={data()}>{data()}</Match>
    </Switch>
  );
}

I'd appreciate any input on what is going wrong here, or why the application is not working as intended.

I created a small project to help me troubleshoot the issue: rcannood/experiment-solidstart-on-firebase.

---

Locally (pnpm run dev), the application looks like this:

When I visit the application hosted on Firebase ( https://solid-project-18cb3.web.app/ ), I get the following:

For good measure, I also deployed the application to Vercel, where everything does work ( https://solid-project-ncfv9j2yb-data-intuitive.vercel.app/ ):

Expected behavior 🤔

I'm expecting the Firebase-deployed application to also say "Hello from the server!".

Steps to reproduce 🕹

I created a minimum reproducible example:

1. rcannood/experiment-solidstart-on-firebase@33460f0: I set up a SolidStart project
2. rcannood/experiment-solidstart-on-firebase@8f7c55f: I enabled SSR in the app.config.ts and set up my Firebase project
3. rcannood/experiment-solidstart-on-firebase@dc6341a: I added a component which fetches data from the server via createResource and "use server"
4. I deployed the application to Firebase with PRESET=firebase vinxi build and npx firebase-tools deploy

Context 🔦

No response

Your environment 🌎

No response

[ryansolid]

I've never tried Firebase before hosting before. I understand it the basic example works but it fails as soon as you try to use server functions?

Is there anyway of getting the error logs from the server? I can see when I can get a chance to sign up and take a look at it but error might guide us to the nature of the problem.

[rcannood]

I understand it the basic example works but it fails as soon as you try to use server functions?

Indeed!

Is there anyway of getting the error logs from the server?

Looking through the logs, I see:

[nitro] [request error] [unhandled] "[object Object]" is not valid JSON
  at JSON.parse (<anonymous>)  
  at parseJSONFromBytes (node:internal/deps/undici/undici:5489:19)  
  at successSteps (node:internal/deps/undici/undici:5470:27)  
  at fullyReadBody (node:internal/deps/undici/undici:4381:9)  
  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)  
  at async consumeBody (node:internal/deps/undici/undici:5479:7)  
  at async Object.Kr [as handler] (./chunks/runtime.mjs:5836:45257)  
  at async ./chunks/runtime.mjs:3076:19  
  at async Object.callAsync (./chunks/runtime.mjs:5453:16)  
  at async toNodeHandle (./chunks/runtime.mjs:3347:7)

Happy to give you access to the Google Project and GitHub repository, if that helps :)

[rcannood]

Maybe just a quick question -- based on the information above, would you be able to make out whether this issue should be posted here in a different repository?

Thanks @ryansolid !

[brenelz]

Can you try nitro v3?

[rcannood]

Sorry, since Firebase wasn't working, I ended up switching to a different provider.

While I can't confirm nor deny that this problem has been solved by switching to nitro v3, shall we close this issue? Or do we leave it open for somebody or something else to try to reproduce this with solidstart v2 and nitro v3?

[brenelz]

We can probably close and someone can reopen if its still an issue. Thanks for rseponding.