[dgesteves-release]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

onsystem@0.11.0

Minor Changes

• #255 ab3f7bc - The ESLint plugin no longer holds up a lint while it looks at the design system again. In an editor, every lint after a pause of two seconds or more waited for that look, which takes longer the larger the design system. Now the lint is answered at once from the design system already loaded, the look runs in the background, and the lints after it get what it found. The lint that starts a look is answered from what was loaded before, so after a change to the design system or the config, the file shows its earlier findings until it is linted again (the next edit, or the next save when the editor lints on save). A one-shot eslint run always loads fresh.

  Edits to the project's config reach an editor's ESLint server without a restart: a rule turned off in the rules or overrides of onsystem.config.json, .mjs, .js or .ts is no longer reported once the plugin has looked at the project again. Before, the plugin kept the rules it loaded first until the server restarted.

  A rule's options can be set in ESLint's config, as in onsystem.config.json: 'onsystem/no-hardcoded-color': ['error', { allow: ['#fff'] }] no longer fails ESLint's config validation ("should NOT have more than 0 items"), and its allow takes the place of the one the project's config gives that rule.

  A misspelled rule in a suppression comment, such as // onsystem-disable-next-line no-hardcoded-colour, is reported by the new onsystem/suppression rule, a warning in the recommended config, with the message check gives. Through ESLint, nothing said why the comment suppressed nothing. This is a new warning on upgrade: a run with --max-warnings 0 over code with such a comment now fails, until the comment is fixed or 'onsystem/suppression': 'off' turns the rule off.

  docs/eslint.md says where rule options live, what each ESLint run pays for the plugin (prefer onsystem check or the GitHub Action for a CI gate), and that ESLint's --cache does not see design-system changes.

Patch Changes

• #254 5638dd2 - onsystem export --format design-md writes Tailwind's spacing unit as the steps of the scale ("1": 0.25rem, "2": 0.5rem up to "96": 24rem) instead of base: 0.25rem. DESIGN.md has no multiplier, so a reader, onsystem included, took 4px as the only step: read back in a project with no stylesheet, padding: "16px" got the advice "Use p-[4px]", and gap-[8px] the nearest step gap-[4px]. Now 8px and 16px are on the scale, and p-[13px] is nearest p-[12px]. Export again to rewrite a DESIGN.md written by an earlier version.

  A typography alias in the DESIGN.md export, such as shadcn/ui's --font-heading: var(--font-sans), is written as the level it names (fontFamily: ...) instead of "{typography.font-sans}". A reference in the front matter names one value, not a level: onsystem warned "unresolved reference {typography.font-sans}" when it read the file, and DESIGN.md's linter reported one unknown typography property per character of the reference.

  A DTCG file exported into the project with onsystem export --format dtcg --out design.tokens.json, which zero config reads back next to the stylesheet, no longer adds tokens. Its @theme inline tokens (rounded-sm, font-sans) have no custom property to merge by, so they now merge with the stylesheet's by name and Tailwind class. In a stock shadcn/ui app, inspect listed 50 tokens instead of 42, and a later DESIGN.md export listed the radii twice and warned that they were left out of the front matter.