Getting started

Content written long after the last deploy (by a scheduled function, a form handler, or a webhook) has to reach templates at build time. This plugin fetches it from Netlify Blobs & keeps a local copy, so builds are fast, work offline, & degrade gracefully when the store is down.

• Node.js 22.12 or newer, the floor set by @netlify/blobs
• Eleventy 3 or newer

# yarn
yarn add @allons-y/eleventy-plugin-netlify-data-store

# npm
npm install @allons-y/eleventy-plugin-netlify-data-store

Register the plugin, then wire the reads wanted into global data. immediate: true runs the plugin during the config file rather than after it, which is what lets the store be destructured on the spot.

import netlifyDataStore from "@allons-y/eleventy-plugin-netlify-data-store";

export default function (eleventyConfig) {
	let { readBlob } = eleventyConfig.addPlugin(netlifyDataStore, {
		immediate: true,
		storeName: "content",
		ttl: "1h",
	});

	eleventyConfig.addGlobalData("activity", () => readBlob("activity"));
}

Reads that reach Netlify Blobs need NETLIFY_SITE_ID & NETLIFY_TOKEN in the environment. A read served from a warm cache needs neither, which is what lets a build run offline.

• How it works: the envelope, the cache, & the order reads resolve in.
• Configuration: every option & what it affects.
• Guides: write from a function, read in templates, & build offline.