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
@brenelz I don't think the mode of failure is the concern on this (ie. there are a number of ways to repro this, this just happens to be one of them), but rather the way in which it's failing.
When this is happening in start, assuming the issues I've faced are the same as this, the error just basically nullifies the entire subtree from where it occurs, meanwhile the app continues running as expected above this level of the component tree. This creates an experience where a portion of your app fails to render with no insight as to why, other than the inferring the rough problematic route by what fails to render.
Thus, I don't think the specific 'use server' placement is the real concern here. It may solve this specific issue, but eg. I'm using start on a project with server: false set, and have experienced similar behavior when using actions on client. The common thread between this and the issues I've faced is the action method itself.
Duplicates
Latest version
Current behavior 😯
useAction
with non trivial server side code causes a silent crash on the client and no errorsExpected behavior 🤔
useAction
with server side code simply worksSteps to reproduce 🕹
Repro repo: https://github.com/shoooe/solid-start-blank-page
Context 🔦
I'm trying to call a server-only action using
useAction
Your environment 🌎
No response
The text was updated successfully, but these errors were encountered: