Replies: 2 comments 2 replies
-
@akomm I'm having what I think is the same issue. If I use Did you ever work this out? |
Beta Was this translation helpful? Give feedback.
-
@akomm I think I've worked out my issue. First, I turned on "preserve log" in Chrome Dev Tools, and then I noticed there was indeed an error in the console. Because it immediately refreshes the page, it was hard to notice this. The error message itself doesn't make any sense to me. When I examined the route itself, I worked out that the issue was caused by this:
export const someFunction = async () => {
...
}
export const action = async ({ request }: ActionFunctionArgs) => {
...
} If I remove the But doing that with Maybe this was your issue too? |
Beta Was this translation helpful? Give feedback.
-
The redirect is not triggered by server, all status 200 and no location headers. It must be the fetcher that triggers the site reload. It only happens after migrating to vite and ruling out all issues (no errors displayed in console / server output).
Without vite there is no full page reload.
The problem: I can't reproduce this with an empty repository, including flat-routes. And sadly I can't share the large codebase :(.
Because of the dependence on plain promise returned vs. await & json(), I can't but think that it might be related to the API changes in preparation for RSC / single fetch that are expected to support promises over the wire.
Beta Was this translation helpful? Give feedback.
All reactions