-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Enhancements for global.fetch #1
Comments
The cache backend should probably be configurable like https://github.com/npm/make-fetch-happen#--optscachemanager This would help when deploying to a serverless environment where the filesystem will likely not be shared across requests. |
Yep, agree 100% @tikotzky. I'm thinking we can add a |
FWIW I included a disk-based cache by default in v0.6.0 but had to roll it back in v0.6.1 because 304's weren't being handled properly (returning |
* S3 file upload (#1) * Implemented S3 upload * Updated README * Cleaned up dependencies * Revert "S3 file upload (#1)" (#2) This reverts commit df2359c. * S3 file upload (#3) * Implemented S3 upload * Updated README * Cleaned up dependencies * Update contributors.yml * S3 file upload (#4) * Implemented S3 upload * Updated README * Updated README * Cleaned up dependencies * Fixed dependencies * Refactored from useActionData to useFetcher
A few small enhancements I'd like to make to the
global.fetch
we provide in node:{ compress: false }
by default. This lets people more easily return the result of afetch
directly from a data loader with the proper encoding..cache/fetch
directory by default for cachingfetch
results. In a long-running server process, this can really speed up the results of afetch
.The text was updated successfully, but these errors were encountered: