Differences from 11ty
Where 11ty builds a page, Brrrty aims to write the same bytes. Everything on this page is about the edges, where it can't yet, or where it chooses to stop rather than guess.
It refuses instead of guessing
When Brrrty can't reproduce something exactly, it doesn't write an approximation. It refuses that page with a code, the file and line, and the reason, and builds the rest. The build exits with status 1, so CI notices.
The same goes for the places where 11ty stops the whole build: a data file that won't parse, two pages with one permalink, a loop in computed data, a filter that throws. Brrrty refuses the pages at fault and writes the others. --strict stops at the first error, as 11ty does.
The config is Rhai
Brrrty doesn't run JavaScript, so eleventy.config.js becomes brrrty.config.rhai; see Getting started and the configuration reference. Without a Rhai config, Brrrty builds with 11ty's defaults and warns that it isn't reading your JavaScript one. With one, the JavaScript file is ignored.
What isn't there yet:
.11ty.jstemplates, and JavaScript data files without a.rhaiport.- Shortcodes, and plugins other than
rssandsyntaxhighlight. - 11ty's
getCollectionItem,getPreviousCollectionItem,getNextCollectionItem,getCollectionItemIndex,inputPathToUrlandrenderTransformsfilters. dir.includes,dir.dataanddir.layoutsother than their defaults.- Passthrough copy with a glob.
addWatchTarget,setServerOptionsandserverPassthroughCopyBehavior.
A plugin your JavaScript config adds and the Rhai port leaves out can't be noticed: Brrrty never sees the JavaScript. Port every addPlugin call.
Filters don't share state
11ty renders pages one after another, so a JavaScript filter can keep a counter or a cache between calls. Brrrty renders pages in parallel, where that could never give the same output, so a Rhai function can't capture outside variables and every argument is a copy. Collection items are read-only for the same reason. The configuration reference shows how to pass fixed values in.
Syntax highlighting has 28 languages
Brrrty's port of Prism has 28 of Prism's 297 languages so far. A fence in one it doesn't have yet is refused rather than left plain.
In 11ty, Prism is shared across the whole build, and loading some languages changes others: regex changes javascript, css-extras changes css, and so on, for every page rendered after. Before it builds, Brrrty reads every fence's language and every {% highlight %} tag in the input folder, and when one of those languages is named anywhere, it refuses the pages whose highlighting would change, naming the file and line that loads it.
Time can be pinned
SOURCE_DATE_EPOCH, a whole number of seconds since 1970, sets the time for now(), Liquid's 'now' and 'today', and feed dates, so two builds of the same source give the same files. Without it, the clock is read as 11ty reads it.
brrrty serve is stricter about the network
It listens on localhost only, answers only requests that name this machine, and never serves a file outside the output folder. A build with errors still serves the pages that built. The full list is on the brrrty serve page.
Small things
- The summary line is Brrrty's own:
Wrote 9 files, copied 6 files in 0.01 seconds (brrrty 0.0.10). Problems print with a code, such asliquid-unknown-filter, and a hint. - Template files that 11ty only reads through a plugin (
.webc,.pug,.mdxand others) are skipped with a warning. - The live-reload script lives at
/.brrrty/instead of/.11ty/.
Every detail, edge case and refusal is in PORTING.md and the changelog.