---
title: 'v0.1.0-next.46'
description: 'A page can split itself on a comment marker, the image shortcode was reworked and now caches, Baseline goes quiet by default, and a dark-mode meta tag stops disappearing.'
slug: '0-1-0-next-46'
type: 'page'
lang: 'en'
url: 'https://www.eleventy-baseline.dev/release-notes/0-1-0-next-46/'
---
The biggest release so far, and it has one new feature and a lot of sharpening. The feature is page breaks: a comment in the body turns one file into several pages, an affordance WordPress has had for twenty years and static site generators have not.
The sharpening is mostly the image shortcode, which was opened up after a consumer forked a hundred and forty lines of it to get past a closed function. Three breaking changes come out of that, and one of them changes the markup on every site that renders an image.
Baseline also stops narrating your build unless you ask it to.
---
## Breaking
{% stepsBlock 'compact' %}
- **A missing `alt` now throws instead of warning.**
The build stops rather than shipping a page with an unlabelled image. This is what `eleventy-img` itself does, and a warning was the wrong tool: it scrolls past, and the page ships either way.
Use an empty string for a decorative image. `alt: ""` is a statement, and it now reaches the output intact where the attribute renderer used to drop it, which had erased the difference between a decorative image and one nobody had thought about.
- _Symptom: a build that stops naming a file and an image, where it used to print a warning you had learned to ignore._
- **Five image options were removed rather than deprecated.**
`imageClass`, `containerClass`, `style`, `attrs` and `figure` are gone. Passing one is ignored, so check your call sites. Two bags replace all five: `img` for attributes on the `![]()
`, `picture` for attributes on the ``, and both take anything HTML takes.
{% raw %}
```nunjucks
{% image {
src: "/media/hero.jpg",
alt: "The valley at first light",
img: { class: "u-rounded", "data-zoom": true },
picture: { class: "c-hero__media" }
} %}
```
{% endraw %}
The migration table is on [[image-shortcode | the image shortcode reference]]. Dropping `figure` fixes a silent data loss on the way past: `figure: false` alongside a `caption` used to return the picture alone and discard the caption, on a green build.
- **`jpeg` joined the default formats, and the `![]()
` fallback changed size.**
Defaults are now `['avif', 'webp', 'jpeg']`, and the `![]()
` inside the `` takes the **largest** rendition of the most compatible format rather than the smallest.
Both halves are about the same thing. The `![]()
` carries no `srcset`, so its `src` is not the first of several candidates a browser picks from: it is the whole answer for anything that reads the markup without rendering it, which is feed readers, scrapers and link-preview bots. Those were being handed the smallest file, described with the largest file's `width` and `height`. With only avif and webp generated there was also no format a client could fall back *to*.
- _Costs a third encode per width. Drop `jpeg` from `media.image.formats` if you would rather not pay it, and the emitted markup on every existing site changes on the next build either way._
{% endstepsBlock %}
---
## Changed
- **Baseline is quiet by default.** You get the startup banner, a version line and one line naming the active modules. `verbose: true` opts into the full narrative. `verbose: false` is a third state and means silence, because saying nothing and saying no are different requests. `warn` and `error` still emit in every state, and Eleventy's own `--quiet` has the same effect as `false`.
- **An asset that does not compile now fails the build.** There is no useful site on the other side of a stylesheet that did not parse, and the error names the file. The dev server is the exception and still degrades to a placeholder comment, because a dead watch loop is worse than a broken reload.
- **`assets.esbuild` reaches esbuild whole.** It never did: the processor read `minify` and `target` off the object and dropped everything else, while the docs said otherwise. `define`, `loader`, `banner`, `external` and the rest all work now. If you have been setting a key that was quietly discarded, it takes effect on this release, and a bad value fails the build where it used to do nothing.
- **A name you already defined stays yours.** Register a `markdownify` filter or an `image` shortcode of your own and Baseline leaves it alone rather than overwriting it, and says at startup which ones it skipped. Eleventy's own warning for this goes to a debug namespace nobody has switched on.
- **The pre-pass stopped building what it throws away.** It no longer compiles the asset pipeline into a dry run whose output is discarded, and the image shortcode uses `statsOnly` there rather than encoding every rendition twice per build.
---
## Added
- **Page breaks.** A `` in the body splits the page into parts, one Eleventy page each, numbered under the page's own URL. The grammar borrows wikilinks, so `` names the part and gives it an entry point. Baseline emits no navigation markup: `_pagebreak` carries the parts and your layout draws the links, the same bargain as `page.translations`. See [[page-breaks | splitting a long page]].
- **Project-wide image defaults.** `media: { image: { widths, formats, sizes } }` at registration, so a house style is set once rather than on every call. A single call still overrides them.
- **A build cache for image renditions.** In a build, renditions are written to `.cache/media/` and copied into the output afterwards, so wiping `dist` or starting from a clean CI checkout no longer costs a re-encode. Nothing invalidates it, deliberately: clearing a cache is your maintenance, not the plugin's. Persisting `.cache` between deploys is one block on Netlify and automatic on Vercel and Cloudflare.
- **Attributes on the inline filters.** `inlineESbuild` and `inlinePostCSS` take an `attributes` object and put it on the `