GuidesLumos 1.0.4New
What changed in v1.0.4
Prettier leaves the framework's own folders alone, and a new site can no longer be published to the npm registry by accident, in Lumos v1.0.4.
Lumos v1.0.4 was released November 14, 2026. This patch keeps the framework's own folders out of your site's code formatting, and marks a new site as private so its source cannot reach the npm registry by mistake. No component, class, prop or token changed — your markup stays exactly as it is.
Prettier leaves the framework's folders alone
Every Lumos site ships with Prettier — the formatter that rewrites your files into one consistent style — and an npm run format script that runs it across the project. A new site also carries two folders that belong to the framework rather than to you: .agents, which holds the skills an AI assistant reads when it works on your site, and .stacki, which holds editor settings.
Those two folders were being reformatted along with everything else. npm run format rewrote files you had never opened, and npx prettier --check . — the command that asks Prettier whether anything is unformatted, without changing it — failed on a site straight out of the installer.
Both folders are now listed in .prettierignore, the file that tells Prettier what to skip:
dist
.astro
node_modules
.agents
.stackinpm run format now touches only the files that are yours, and npx prettier --check . passes on a fresh site. The framework's own checks scaffold a site and run that command on it, so it stays that way.
New sites are marked private
npm publish is the command that uploads a package to the npm registry, the public library of code that npm install downloads from. It is meant for libraries, not for websites — but nothing stopped it running inside a site folder, and it would have put that site's source on a public registry under the folder's name. On client work, that is a client's code published by accident.
A new site's package.json now carries one extra line, and npm refuses to publish any package that has it:
{
"name": "my-site",
"private": true,
"type": "module"
}Updating an existing site
Both changes live in files your own site owns. The Lumos upgrade workflow replaces the framework's components and styles, and it deliberately leaves your package.json and .prettierignore alone — so these two are yours to make, and they are the whole update:
- Open
.prettierignorein your project's top folder and add.agentsand.stacki, each on its own line, at the end. - Open
package.jsonand add"private": true,as a new line directly under the"name"line. The comma at the end matters — every line in that list but the last one has one.
Then run these from your project folder to reformat with the new rules and confirm the site still builds:
npm run format
npm run check
npm run build