Skip to content
opsinjs
Edit this page

opsinjs

Changelog

What changed in each release, newest first, and the versioning and deprecation rules every release follows

Breaking changes lead each entry. A changed presentation default, such as a status word, a default rounding or a unit, leads it on its own line labelled SAFETY, because a consumer who copied a file receives the change only when they copy it again. opsinjs owns no clinical threshold, and no entry reads as though it does. A feed is at /rss.xml.

Not written yet.

Sixty components were built after 0.0.0 and no entry records them. Every catalogue row still reads since: unreleased, so the version number to file that entry under is the decision blocking it.

11 November 2026

Five interaction motions, each on a spring the motion tokens already kept for that job, and all set out on Motion. A button sinks under a press and settles back as you let go, and so do a button-shaped link and the close controls on a dialog, a sheet and a toast. A linked card or metric tile sinks a little less and never springs, because it can hold a reading. The switch thumb squashes while you hold it and travels when you let go, a tick draws itself and a radio dot grows from the centre. The chosen segment of a segmented control is one puck that glides to your next choice. The tab indicator glides too, where it used to jump, because its transition named the wrong property. Popovers, menus, selects, comboboxes and tooltips unfold from the control that opened them and come into focus, where menus, selects and comboboxes used to appear in a single frame. A toast rises from its edge, follows a finger that swipes it, springs back if let go early and leaves the way it was thrown, and a toast docked to the top now swipes up rather than down. Under reduced motion every one of them still changes state, with no travel, squash, scale or blur. Value, RangeBar and ScoreDial still never animate. None of it has had an accessibility review. This entry carries no version number.

10 November 2026

StatusPill is an enamel plate, lit from above, with a semibold word. Its colours are new, and they are not the status ramp: Steady is emerald, Watch is gold, Needs attention is burnt orange and Urgent is crimson, each at the lightness where its hue reads as itself, and the same in both themes. The word is white on the three deep plates and deep brown on the gold one. The four plates are new tokens in tokens/color.json, such as --opsin-status-urgent-plate, and the build refuses a plate whose word falls below the body-text floor. On paper the pill still prints as the level's tint with its ink. The words, the glyphs, the sizes and the props are unchanged. None of it has had an accessibility review or a clinical review. This entry carries no version number.

8 November 2026

The accent is yours to choose now. There are three accent themes, each with the same nine accents: normal keeps the ink action and spends the accent on what is selected, vibes makes the accent the action at full chroma, and stryk is high contrast, applied on its own whenever a reader's system asks for more contrast. Set them with data-accent-theme and data-accent, or install a theme item such as opsinjs-vibes-volt. In the default theme a switch that is on, a ticked box, a chosen radio, a slider's range, a progress fill and a chosen scale point are cobalt rather than ink. A quiet button and a card's quiet action are set in the accent ink and are no longer underlined; only a link inside running text keeps its underline. Every accent pair is measured, and the build refuses one below its floor. None of it has had an accessibility review.

Six components were redrawn, and none of them claims anything new. RangeBar is a glass gauge: the range is a lit section inside a glass tube, and the reading is a frosted cursor that rides the tube with an index line in the level's colour; RangeLegend draws each tone as a miniature of that piece. ScoreDial is an instrument, with a bezel, a ruled face, the scale's two ends and a needle on a hub. GoalRing sits on a plate and now draws in its category colour, which a class naming a missing utility had turned to black. StatusPill draws its glyph in the level's line colour, solid for the two upper levels, inside a softer capsule. AlertBanner is a sheet tinted by its level, with the recommended action filled in the level's own ink. Button labels are centred on the lowercase band a reader sees as the text, rather than sitting a pixel and a half low.

Page titles no longer end in the site name. A browser tab or a search result shows the page's own title, such as "Button", because search engines already print the site name above every result. The home page title reads "opsinjs: a design system for consumer health apps". The landing page footer links to Pensieve Labs and to its open source hub, and every page now names Pensieve Labs as the publisher in its structured data. Several component descriptions were shortened to fit a search result, with no change to what they claim. This entry carries no version number.

The system has a new look, and it changes no claim any component makes. The primary action is ink, a near-black capsule by day and a near-white one by night, so the two colour axes are the only colour that carries weight on a product screen. One brand blue is left, and it is spent as light: the focus ring, the mark beside an eyebrow and the bloom behind this site. Cards keep their opaque fill and gain a larger squircle corner, a soft drop and a decorative edge, while controls keep their 3:1 boundary. Buttons, chips and segmented controls are capsules, and a quiet button is underlined so it still reads as a control. The squircle token reads superellipse(2) now, because the superellipse(4) it held drew a nearly square corner. Product titles are set at 800, body text sits on a 24px line, and the RangeBar reading is a ringed disc, as the opsinjs mark draws it. This site sets Inter heavy and tracked in, with a floating glass sidebar. None of it has had an accessibility review or a clinical review.

13 October 2026

Each screen on the showcase now opens on its own at /showcase/<slug>. The screen fills the window and nothing is drawn round it except a small bar in the top right corner, which switches between light and dark and between phone, tablet and desktop sizes without reloading the screen, so whatever you typed into it stays. On a window narrower than 1024px the screen starts below the bar, so the bar never covers it. The results screen has a page there too, so both cards open the same way. The essay that used to stand at /showcase/diabetes-medicines-app is gone, and the address now opens the app itself. The two component defects it recorded are tracked as issues #16 and #17. The bar also carries a link back to the showcase, for a reader who arrived from search. A screen framed on a documentation page also fills its frame edge to edge now, with no grey margin round it. This entry carries no version number.

The showcase has a third screen, the patient record portal: a patient's own view of the record their hospitals write, with who can see it, who has looked at it, the people they trust, a share a doctor opens once and an emergency card a paramedic can read. It is built from twenty-four components and lays itself out for a phone, a tablet and a desktop window, following the reader's text size as well as the window's width. Everything in it is invented, it explains nothing it shows, and like every screen on the showcase it has had no clinical review.

12 October 2026

The site has a landing page at /, with links to the documentation and to GitHub, and the documentation moved under /docs: this page is now /docs/changelog, and the index twin is /docs.md. Every address from the last three weeks, such as /components/button, redirects permanently to its /docs twin, and so does its .md twin. The registry under /r did not move. The development warnings in lib/opsinjs.ts now link to /docs pages; a copy installed earlier prints the old addresses, which still resolve. This entry carries no version number.

The landing page also links to the showcase, which now shows a card for each whole screen opsinjs has built from its own components: the diabetes medicines app and the results screen. Both are opsinjs's own work with invented figures, and neither has had a clinical review. The bar an entry from another team has to clear is unchanged.

8 October 2026

The documentation site was restructured into six sections modelled on Blueprint's docs: opsinjs, Foundations, Components, Health, Patterns and Reference. It has about 115 pages where there were 400, and each old URL redirects to the page that absorbed it. If a stored address stops answering, find the page again in /llms.txt. This entry carries no version number.

The GitHub repository became public the same day. Every page now links to its source with "Edit this page", the sidebar and the footer link to the repository, and issues, discussions and private vulnerability reporting are open. The site also sends security headers with every response, including a Content-Security-Policy that admits nothing from another origin.

A seventh sidebar section, Contribute, is a plain-language guide for clinicians and health scientists who want to contribute with Claude Code: setting up, every step with an example prompt, three worked examples and what not to do.

2 September 2026

Version 0.0.0 was the scaffold. It shipped a documentation site, a token layer, twenty-four component specifications at planned, eight decision records and the machine surfaces, which were the .md twins, /llms.txt, the /r catalogue and an offline bundle. It contained no components and published nothing to npm.

Versioning

opsinjs follows semantic versioning, and the versioned surface is wider than the JavaScript API, because you own the source and your styles and tests reach into the markup. Five surfaces are covered:

  1. The exported API: components, hooks, functions, types, and their prop names, types and defaults.
  2. The rendered DOM: structure, nesting order, roles and accessible names.
  3. The data-* attributes listed in Data attributes.
  4. The CSS custom properties listed in CSS variables.
  5. The registry contract: item names, the URLs they are served from and the files each installs.

Removing or renaming any of these, or changing the condition that produces it, is a major version. Exact token values are not covered, though a token's meaning and its contrast floor are. Nor are class names, CSS variables without the --opsin- prefix, anything marked @internal, or this site's own chrome.

Before 1.0, a minor release may break something, with a changelog entry and a migration note, and a patch never deliberately does. Token names are not stable yet, but token meanings are. A shipped component's API may change in any release, with a changelog entry rather than a deprecation cycle. Nothing in a copied file records its version, so run shadcn add in its own commit naming the item and the date.

Deprecation

Nothing is removed without being deprecated first. A deprecated component, prop or token keeps working for at least one minor release before 1.0 and a full major after it. Its entry names the replacement, the version that deprecated it and the version that removes it. Treat it as absent for new work. Nothing has been deprecated yet.

The deprecation list has not been generated.

No script projects deprecations out of registry/catalogue.ts yet.

Nothing on this site types a measured number by hand, so an ungenerated table shows this rather than an example.

What is next

There is no dated roadmap. Open items, in no order:

  • An independent accessibility review. The WCAG 2.2 AA audit so far was run by the components' own authors.
  • A clinical review. No component has had one, so nothing here is for a production health surface.
  • ESLint and Stylelint rules that enforce the two colour axes and tokens in your own project. They are planned, not built.
  • Source data for the keyboard reference and for bundle sizes.
  • Internationalisation, deferred rather than blocked. Unit systems such as mmol/L and mg/dL already ship.

Not planned at all: clinician-facing components, a charting library, a general form library, an opsinjs CLI and native mobile.