Issue with node-fetch #1817
Unanswered
lukebennett88
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a Remix app as part of a turborepo monorepo and deployed on Vercel.
It's pretty simple at this point, basically just the turborepo-vercel examples with a few personal preferences.
The source is here:
https://github.com/lukebennett88/remix-turborepo-vercel
I've deployed this to Vercel, and the app is loading just fine:
https://remix-turborepo-vercel.vercel.app/
I then added some code to build pages from Sanity (see diff here: https://github.com/lukebennett88/remix-turborepo-vercel/tree/add-sanity).
This works fine locally, but when I deploy I get the following error:
If I take a look at the source for PicoSanity I can see that
node-fetch
is a dependency which is passed in as the second param of theClient
function, and inside of the Client function I can confirm that the second param of the function is referred to as "fetcher", so it looks to me likenode-fetch
is not getting bundled correctly (maybe I need to do something with Rollup?).The other thing I should mention is that the diff I showed above was squashed and merged from another branch that I have since (foolishly) deleted. The deleted branch is where the message above comes from. For some reason the deploy preview from squashing and merging the commits 404s instead of showing the error boundary. If I look at the build in Vercel it seems the that
/build
folder doesn't exist, only the/api
folder. The code is exactly the same, so I can't explain why this would be the case.Beta Was this translation helpful? Give feedback.
All reactions