blank page on error
on occasion if there's an error that doesn't pop up in console or on my server, the route will just appear blank, with only the parent layouts rendering.
this happens somewhat frequently as i'm newer to solid, and debugging it is a pain. i don't really know how to better explain it than that somewhere in the filetree my components just stop rendering but no errors show up anywhere
i can send a screen recording if it'd help, but just wondering if this sounds like a familiar bug or something that others have run into
13 Replies
I'm experiencing the same.
In my case it's probably related to the use of
createAsync
. Are you using the same by any chance?I did, it doesn't show anything.
With
createAsync
, maybe you're losing reactivity somehow, so you never learn that the async resolved and thus don't update the display?I've actually pinned it down to using an action
Via
useAction(actionName)
I think same issue for me
Ok this is fun. So for me the problem was a top level constant that used
serverEnv
as in:
If I remove that or if I use "use server"
at the top of the file then everything works fine.
Server env is declared as:
So I'm guessing it's the accessing of process.env
outside of the "use server" context that caused the issue.
Another case (and easiest to reproduce):
If I have a module x
:
and call signInWithGoogle
from a route page:
No errors on console or server but console.log
is never shown.
If you comment out const signIn = useAction(signInWithGoogle);
then the console log is shown on the client as expected.Repro repo: https://github.com/shoooe/solid-start-blank-page
GitHub
GitHub - shoooe/solid-start-blank-page
Contribute to shoooe/solid-start-blank-page development by creating an account on GitHub.
Cool! Now that you have an easy reproduction, maybe worth elevating this to a GitHub issue on solid-start.
Yup, done 👍
GitHub
[Bug?]:
useAction
causes silent crash on the client · Issue #168...Duplicates I have searched the existing issues Latest version I have tested the latest version Current behavior 😯 Using useAction with non trivial server side code causes a silent crash on the clie...
Just to be sure: is this an actual bug or am I missing something stupid?
or were you able to resolve yours?
I’m not sure what causes it
Because of the layout, I can figure out pretty quickly what level of the component tree the breaking page is at
But then it’s just a matter of isolating pieces of code to find where the error happens