Repository navigation
useFetcher not working for routes that has runtime nodejs #129
Description
I have encountered an issue while using useFetcher in Remix. When utilizing useFetcher for a route configured to run on the Edge Runtime, the route is successfully called. However, when the route is set to run on the nodejs runtime, useFetcher returns a 404 Not Found error.
Reacted by Tyler Fisher and Joost Jansky
Activity
TooTallNate commentedon Aug 15, 2024
Can you put together a reproduction repo so that we can take a closer look?
joeykamsteeg commentedon Aug 15, 2024
@TooTallNate Sure, I'm on it!
joeykamsteeg commentedon Aug 15, 2024
I have made a reproduction repo and running on Vercel, their is a strange twist. In my personal project the node function is not working with
useFetcherbut in this reproduction repo the Edge function is not working 😅 but the issue is the same.Extra information: If you try to press the buttons on the live version, you see that only the NodeJS action is popup up in the Network in the inspector. I'm not sure if this is related to 'Single Fetch'
Repo: https://github.com/joeykamsteeg/remix-usefetcher-vercel-issue
Live: https://remix-usefetcher-vercel-issue.vercel.app
[-]`useFechter` not working for routes that has runtime `nodejs`[/-][+]`useFetcher` not working for routes that has runtime `nodejs`[/+]joeykamsteeg commentedon Aug 15, 2024
I have setup a new branch without singleFetch and it seems an issue while using Single Fetch
live: https://remix-usefetcher-vercel-issu-git-c14bdc-joey-kamsteegs-projects.vercel.app/
styxlab commentedon Feb 25, 2025
Looks similar to remix-run#10494. Not sure if this is a pure Vercel or a remix issue. It smells more like a design issue in remix, when single fetch and lazyRouteDiscovery is turned on.