Skip to content

Changelog

What each version of TaishoDS Core brings. While the major version is 0, a minor version can bring breaking changes, and they are announced here.

What's next: the roadmap

0.16.0

View on npm

Added

  • taisho mcp: a local MCP server for coding assistants. It runs on the user's machine over stdio, is read-only, and uses no network and sends no telemetry. It has six tools: list_components (the list of components, with its total), get_component (one component's reference: what it is, when to use it, examples and keyboard), search_utilities (searches utilities by name and says how many matched), validate_markup (checks markup against the system's rules), translate_tailwind (converts markup with Tailwind classes, using the same table as taisho migrate --from tailwind) and get_theme (the project's theme). It accepts --config and --lang. The package adds the mcp/ folder, with the HTML examples and the prose of each component, per language.
  • taisho init offers to install lucide-static. It asks, and installs it with the project's package manager (npm, pnpm, yarn or bun). The --install-icons flag answers yes without asking. Without an interactive terminal it does not install: it prints the command.
  • A guide for AI assistants. The site publishes /llms.txt and /llms-full.txt (the Spanish ones under /es/) and one Markdown sheet per component (/docs/<component>.md), with the rules for writing the markup.
  • New documentation: the "AI assistants" guide (llms.txt, the sheets and the MCP server, with the setup for each client), the command-line reference (init, generate, watch, check, migrate and mcp, with all their flags), the negative margins rule in the class naming guide and the "Footer or menu link" example on the Link page.

Changed

  • taisho migrate --from tailwind and the translate_tailwind tool convert every negative margin. They used to know only -m-1, -m-2, -m-4 and -m-8; now -mx-2 becomes mx-neg-8, -mt-4 becomes mt-neg-16 and -ml-4 becomes ms-neg-16 (logical side), and so on for the other sides and steps. What is not on the scale (-mx-96) is reported as having no equivalent, with the reason. The utilities already existed: the CSS does not change.
  • Keyboard focus on links and navigation rises to the same color as with the pointer. The subtle link (variant="subtle") and the links or items of the breadcrumbs, the page index, the sidebar, the navigation bar and the pager took their full color only with the pointer; now they take it on keyboard focus too, in addition to the focus ring. The markup does not change.
  • taisho generate warns about lucide-static only when icons in use cannot be resolved because the package is missing, and says what follows from it.
  • On Windows, the paths taisho generate prints to paste into the HTML use /, as the browser sees them.
  • The package's NOTICE file names the Lucide icons Core includes (the paths used by core.js and the examples in mcp/) and carries the text of their license.
  • Near-pure blues stay exact on their step. With colors like #0000ff or #0000cc, the palette engine clipped the starting color's chroma even though an sRGB screen could show it, and the step came out as a different blue (#0031e5 instead of #0000ff) with no notice. A color that is already inside the gamut is no longer clipped. Only those blues change; every other palette comes out the same.
  • A color right at the edge between two steps is no longer shifted. The palette engine could send it to the neighboring step and move it slightly, even though its own step contained it; that happened in 10 of 8,192 test scales. And a starting color whose value changed by 1 in 255 when written with four decimals is now written with as many as it takes to stay exact.

0.15.1

View on npm

Added

  • New out field in taisho.config.ts: the output folder. Precedence: --out, then the config's out, then ./taisho next to the config file. It is read by taisho generate, watch, check and migrate, and by the Vite plugin.
  • taisho init asks for the output folder. It suggests ./taisho when package.json declares a bundler (Vite cannot import JS or CSS from public/), otherwise public/taisho or static/taisho when those folders exist.
  • taisho generate always copies the behavior JavaScript to the output folder. Before, without content, the printed line pointed into node_modules. The lines to paste use the path the browser sees.

Changed

  • Breaking: the default output is now relative to the config file, not to the directory where the command runs. It only differs when using --config other/path without --out: the output used to go to ./taisho in the current directory and now goes to ./taisho next to that config. Pass --out or set out in the config to keep the previous location.
  • The README, the consuming guide (CONSUMING.md) and the docs no longer link anything from node_modules, and add a section on imports for bundlers.

0.15.0

View on npm

First public release of TaishoDS Core: the system CSS, the tokens and the behavior JavaScript, for any HTML page, under the MIT license. It is a beta: while the major version is 0, a minor version can bring breaking changes, and they are announced here.

What it is

TaishoDS Core is HTML, CSS and JavaScript, with no framework. Components are written as markup with classes (class="ts button variant-primary") and data-ts-* attributes; the optional JavaScript makes them interactive.

What it includes

  • 56 components: 38 with behavior JavaScript, 2 native to the browser and 16 plain HTML and CSS.
  • Tokens, utilities and a light and dark theme derived from a seed color, with accessible contrasts calculated.
  • createTheme() to change the theme in the browser.
  • The taisho command, with init, generate, watch, check and migrate: it builds only the CSS each project uses, with its brand and its fonts, and checks the classes you write.
  • A Vite plugin at @taishods/core/vite.
  • TypeScript types compatible with node16, nodenext and bundler module resolution.
  • JavaScript texts in Spanish and English, according to the lang attribute.

Ways to use it

  • From a CDN, with nothing to install: two <link> tags and a <script type="module"> from https://taisho.design/core/0.15.0/, with integrity and crossorigin. The version is fixed in the URL.
  • Compiled, with your brand in the CSS: npm i -D @taishods/core, npx taisho init and npx taisho generate.

Requirements

  • Node 22.18 or newer for the taisho command and the Vite plugin. With an older version, the command exits with a message that explains it. The CDN needs no Node.
  • Browsers: the floor is Baseline "widely available" as of November 10, 2026, that is Chrome and Edge 124, Firefox 125 and Safari 17.4 (also on iOS). What goes beyond that floor has a fallback or degrades without losing functionality; it was not tested in browsers at those versions.

Known limits

  • Not tested with screen readers (VoiceOver or NVDA) or on a real iPhone or iPad. It is tested with axe, with computed accessible names and descriptions, and with keyboard and focus in desktop Chromium, Firefox and WebKit; the CDN quick start is also tested on WebKit with an emulated iPhone, which is not a real iPhone. There is no formal ACR/VPAT (accessibility conformance report).
  • Frameworks tested with the real package (Modal and Select, in development and in production, on Chromium, Firefox and WebKit): Astro 7.4.12 and 6.4.8 (static output), Next 16.4.6 (App Router, Turbopack, static pages) and SvelteKit 3.2.0 (with adapter-node). Vite, with no framework and with the plugin, is tested in the repository's continuous integration. Any other framework, version or deployment mode was not tested and is not claimed to work; the details are on the Compatibility page of the documentation.
  • A component that the framework controls with its own state (for example, a hidden or an aria-expanded that the component updates) was not tested: Core writes those attributes in the DOM.
  • The behavior JavaScript touches document when it loads: in a framework with server-side rendering it is loaded only in the browser.
  • A custom theme requires compiling with taisho generate; the CDN serves the TaishoDS theme.
  • The API is 0.x and can change between minor versions.

Reporting a problem

Bugs and proposals go to the Issues of the repository; vulnerabilities, through the procedure in SECURITY.md.