0.1
Elevate 1.2
Before Verso could start, Elevate needed a watcher that keeps up, restarts on design changes, and an API other tools can call.
Verso renders pages itself and asks Elevate for the CSS, so Elevate had to work as a library, not only as a command. These changes shipped as Elevate 1.2.0 and 1.2.1 on npm.
A watcher that keeps up
- Elevate compiles once on start, then again whenever a template is saved, added or deleted. CSS from deleted templates no longer lingers.
Watchtakes a list of folders, so templates, blocks and scripts can all be scanned.- Saving a file in
config/,design/orrules/restarts the compiler, so new tokens apply at once. Saving anExtendfile recompiles.
Commands and an API
- New commands:
buildcompiles once and fails loudly,checknames every bad class in a list, anddescribeprints the design system as JSON. core/api.tsexportsbuild,validate,describeandscan, with no side effects on import. Verso's checks, block builder and design editor all use it.
$ npx elevate-framework check "font:bodoni:h3 text:proof"
$ npx elevate-framework describe --json
import { validate } from './elevate/core/api.ts';
const { problems } = validate('pd:d4 text:ink');
Safer upgrades
- Running
prepareagain replaces onlyelevate/core, keeps the old core in.elevate-backup/, and leaves config, design, rules and templates alone (1.2.1). - A failed build no longer hides scan errors, and
elevate.cssis written in one step instead of being emptied first. - Earlier fixes along the way: breakpoint classes stay on their own elements, hex colours work inside pass-through values, and grid columns can't be stretched by long content.