We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I’m following the docs here:
https://www.11ty.dev/docs/plugins/serverless/#re-use-build-time-cache-from-the-fetch-plugin
So, here's a test case to describe my issue. Here are two URLs:
/build/ /serverless/
Hit the serverless endpoint, and with every hit you'll see the log that it's fetching:
[11ty/eleventy-fetch] Fetching: https://dummyjson.com/products/1
https://github.com/ryangittings/11ty-serverless-fetch-issue
I’d expect the build cache to be reused and the URL not to be hit.
The text was updated successfully, but these errors were encountered:
Huh. Well, this is definitely a bug!
Using dryRun actually prevented both file reads and writes, when clearly we want to allow reads.
dryRun
This will ship with Eleventy Fetch 4.0.0
Sorry, something went wrong.
Awesomesauce! Can I use a patch or a specific branch in npm in the meantime?
This will ship in the next hour or two just going through the rest of the backlog on this repo first
7cb9b8a
(it’s on github now)
4.0 has shipped!
zachleat
No branches or pull requests
I’m following the docs here:
https://www.11ty.dev/docs/plugins/serverless/#re-use-build-time-cache-from-the-fetch-plugin
So, here's a test case to describe my issue. Here are two URLs:
/build/
/serverless/
Hit the serverless endpoint, and with every hit you'll see the log that it's fetching:
[11ty/eleventy-fetch] Fetching: https://dummyjson.com/products/1
https://github.com/ryangittings/11ty-serverless-fetch-issue
I’d expect the build cache to be reused and the URL not to be hit.
The text was updated successfully, but these errors were encountered: