-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warning about unsupported fetch options #2015
Comments
FTR: Original discussion started in https://discord.com/channels/770287896669978684/943924040962306098 |
Actually, I found the CF workers' version of Once that is documented, we could add a note to https://github.com/remix-run/remix/blob/dev/packages/create-remix/templates/cloudflare-workers/README.md to improve the developers' expectation when working with this particular deployment target.. (though, not sure how And if those differences get fixed in CF, we could even close this issue 😅 |
@Aprillion Hey ! More than a year passed since you opened that issue, do you know if it's still applicable today? 🙏🏼 |
no idea, once I stopped using the then-unsupported fetch options, I never had a use case to use those again |
Fair enough :) |
What version of Remix are you using?
1.2.1
Steps to Reproduce
await fetch(..., {cache: 'force-cache'})
inhttps://github.com/Aprillion/stampy-ui/blob/9487ca0319a79f313a38de3744396b3534cacac0/app/routes/index.tsx
Expected Behavior
Some warning about unsupported fetch options, e.g.:
Additionally, if some server environments (will) support native-like HTTP Cache, it would be nice to be able to debug server side fetch requests (similar to browser Network tab) => any documented advice how to debug server fetch would be appreciated too.
Actual Behavior
Everything worked fine locally, then I got an error after deployment to workers:
The text was updated successfully, but these errors were encountered: