mirror of
https://github.com/svemagie/blog-eleventy-indiekit.git
synced 2026-04-02 08:44:56 +02:00
Introduce shared cachedFetch helper (lib/data-fetch.js) wrapping EleventyFetch with two protections: - 10-second hard timeout via AbortController on every network request, preventing slow or unresponsive APIs from hanging the build - 4-hour cache TTL in watch/serve mode (vs 5-15 min originals), so incremental rebuilds serve from disk cache instead of re-fetching APIs every time a markdown file changes All 13 network _data files updated to use cachedFetch. Production builds keep original short TTLs for fresh data. Targets the "Data File" benchmark (12,169ms / 32% of incremental rebuild) — the largest remaining bottleneck after filter memoization. Confab-Link: http://localhost:8080/sessions/0b241cd6-aff2-4fec-853c-2b5a61e61946
35 lines
871 B
JavaScript
35 lines
871 B
JavaScript
/**
|
|
* Podroll Status Data
|
|
* Checks if the podroll API backend is available at build time.
|
|
* Used for conditional navigation — the podroll page itself loads data client-side.
|
|
*/
|
|
|
|
import { cachedFetch } from "../lib/data-fetch.js";
|
|
|
|
const INDIEKIT_URL = process.env.SITE_URL || "https://example.com";
|
|
|
|
export default async function () {
|
|
try {
|
|
const url = `${INDIEKIT_URL}/podrollapi/api/status`;
|
|
console.log(`[podrollStatus] Checking API: ${url}`);
|
|
const data = await cachedFetch(url, {
|
|
duration: "15m",
|
|
type: "json",
|
|
});
|
|
console.log("[podrollStatus] API available");
|
|
return {
|
|
available: true,
|
|
source: "indiekit",
|
|
...data,
|
|
};
|
|
} catch (error) {
|
|
console.log(
|
|
`[podrollStatus] API unavailable: ${error.message}`
|
|
);
|
|
return {
|
|
available: false,
|
|
source: "unavailable",
|
|
};
|
|
}
|
|
}
|