GuidesLumos 1.0.3New

What changed in v1.0.3

The breakout ContentWrapper variant lines up on Windows, Grid's --_fit is valid on its own, and new sites no longer carry the framework's README, in Lumos v1.0.3.

Lumos v1.0.3 was released November 8, 2026. This patch fixes the alignment of the breakout wrapper on Windows, tidies one custom property in Grid, and updates the Astro toolchain. Your component names, paths and props stay the same.

Breakout wrappers line up on Windows

A ContentWrapper with variant="breakout" lets its visual run past the container edge, and it measured that width with 100vw. On Windows, 100vw counts the classic scrollbar — around 15px — so the breakout came out wider than the page and sat about half a scrollbar too far left. Text inside it no longer lined up with the content above.

Platforms with overlay scrollbars, which includes macOS and most phones, never showed the problem. The breakout now measures the section rather than the window:

css
.section {
  container-type: inline-size;
}

.content_wrapper.breakout {
  width: 100cqi;
}

100cqi is the inline size of the nearest container — here the section, which has no scrollbar in it. 100% would not work, because the wrapper's parent is .containerPatternwidth: var(--site-width)max-width: var(--max-width-main)display: flex, which already sits inside the site margins.

Nothing in your markup changes, and the fix needs no new props.

Grid's --_fit is valid on its own

--_fit in Grid held a bare parenthesised expression rather than a calc(). It rendered correctly, because --_track only ever substitutes it inside max(), where a parenthesised calc-sum is already valid. Wrapping it means the custom property stands up wherever it is used:

css
--_fit: calc(
  (100% - (var(--_max-cols) - 1) * var(--_gap-size)) / var(--_max-cols)
);

autofit and autofill grids look exactly as they did. There is no visual change.

New sites no longer carry the framework README

A site scaffolded with npm create lumos@latest inherited the framework's own README.md. It describes Lumos rather than the site built with it, and its banner pointed at a file that scaffolding withholds — so every new project started with a broken image and a build badge pointing back at the framework repository. New sites now start without it.

Existing sites are unaffected. If you kept that README and want it gone, deleting it is safe; nothing reads it.

Astro 7.4.7

The template moves to Astro 7.4.7 along with its integrations. The minimum Node version is unchanged.

Updating an existing site

Use the Lumos upgrade workflow to bring in the fixes while keeping your own changes. After the component and package files are updated, run these from your project folder:

sh
npm install
npm run check
npm run build