pdehaan
commented
2 years ago @ashur Yeah, .addNunjucksAsyncFilter() has a bit of an unexpected signature (spoiler: it uses callbacks).
/**
* @typedef {import('@11ty/eleventy/src/UserConfig')} EleventyConfig
* @typedef {ReturnType<import('@11ty/eleventy/src/defaultConfig')>} EleventyReturnValue
* @type {(eleventyConfig: EleventyConfig) => EleventyReturnValue}
*/
module.exports = function (eleventyConfig) {
const sleep = (ms=2000) => new Promise(resolve => setTimeout(resolve, ms));
https://www.11ty.dev/docs/languages/nunjucks/#asynchronous-nunjucks-filters
eleventyConfig.addNunjucksAsyncFilter( "greet", async (name, cb) => {
await sleep(3000);
return cb(null, `Hello, ${name}`);
});
return {
dir: {
input: "src",
output: "www",
}
};
};---
# index.njk
---
<p>{{ "Dolly" | greet }}</p>OUTPUT
<p>Hello, Dolly</p>> eleventy
[11ty] Writing www/index.html from ./src/index.njk
[11ty] Wrote 1 file in 3.03 seconds (v1.0.2)
ashur
Summary
Using asynchronous filters registered with
addNunjucksAsyncFilterseems to cause builds to exit prematurely.Environmnent
1.0.2/2.0.0-canary.15Steps
addNunjucksAsyncFiltereleventyConfig.addNunjucksAsyncFilter( "greet", async (name) => { return
Hello, ${name}; });npx eleventyto build the sitenpx eleventy --serveto start the built-in serverExpected Results
Building the site will log something like this to the terminal:
showing that the file has been built as expected. (See Attachments below for DEBUG logs.)
Starting the built-in server will log something like this to the terminal:
and continue running until the command is terminated. (See Attachments below for DEBUG logs.)
Actual Results
The file is not built:
The built-in server never starts, and the command exits automatically:
Frequency
Workaround
For projects using Eleventy 2.0, registering the filter using
addAsyncFilterworks as expected.Attachments
Debug
buildlogsDebug
servelogs