Zach Leatherman

@tomayac It’s a global prop on the default export. If you `DEBUG=Eleventy:Image` (https://www.11ty.dev/docs/debugging/) it will show you the concurrency value and the state of the queue. ```js import eleventyImage, {...

Added some Node.js CPU profiling docs, should roll up with the next production build here: https://www.11ty.dev/docs/debug-performance/#node-js-profiling

Via the image transform maybe an `eleventy:optional` attribute that will remove remote images that fail. The impetus use case here is build-time opencollective avatar images on 11ty.dev

Milestoning to 6.0.0

Important reference to #252 which unlocks the use of native fetch and AbortSignal for timeouts https://github.com/11ty/eleventy-fetch/releases/tag/v5.0.0

Shipping with v6.0.0-beta.1

Moving `eleventy:optional` attribute to #259

Whoa—I wasn’t aware of this limitation. We are currently diversifying our website hosting—at this very moment all of the versioned subdomains https://www.11ty.dev/docs/versions/ are on Vercel, one API service on AWS...

I assume you’re referencing https://www.11ty.dev/docs/dates/ specifically:  Eleventy currently runs the entire build and transforms all input files and writes all files to the output directory. So yes, the file...

Are you saying that lastmod and current time are different? I would assume that most of the time (during local dev) they will be the same. Relevant code: https://github.com/11ty/eleventy/blob/556f2d83196a3845e34b1d7f23c6cef2365f0e66/src/Template.js#L656 Docs:...