Skip to content

Compatibility

What your project needs and which browsers are supported. The underlying rule is that TaishoDS bets on the modern web platform, but every new feature has a fallback—nothing breaks if the browser doesn’t have it yet.

Project environment

With Core from the CDN there are no requirements. It’s two <link> tags and a <script>, with no framework and no bundler (see Installation). If you install @taishods/core to use the CLI, you need Node 22.18 or newer, because the generator uses fs.globSync. If something doesn’t show up or doesn’t work, check Troubleshooting.

The Vite plugin (taisho(), from @taishods/core/vite) assumes a Vite project.


Frameworks

Core is HTML, CSS, and JavaScript, with no framework. This table says where it was tested with one in the middle, with exact versions; what isn’t listed here wasn’t tested and isn’t claimed. Each test installs the real package (the Core’s npm pack) into a fresh project, follows the steps in Installation (taisho init, taisho generate, importing the CSS and the JS) and, in Chromium 156, Firefox 157, and WebKit 27.2 (Playwright 1.64.1), checks that the console stays free of errors and warnings, that the Modal opens and closes (with the button and with Escape), that the Select opens, picks an option, and reflects the value, and that everything still works after navigating to another page and back. The test scripts are in the Core repository (smoke-astro.sh, smoke-next.sh, and smoke-sveltekit.sh).

Framework Node What was tested
Astro 7.4.1224.12.0astro dev, astro build + astro preview (static), CSS and JS from taisho generate, CSS and JS from the package, the taisho() plugin, and client navigation with <ClientRouter />
Astro 6.4.822.22.3The same as in Astro 7
Next 16.4.6 (App Router, React 19.3.1, Turbopack)22.22.3next dev, next build + next start (static pages), CSS from taisho generate in the server layout, three ways to load the JS from client components, and client navigation with <Link>
SvelteKit 3.2.0 (Svelte 5.57.3, Vite 8.3.8, adapter-node)22.22.3vite dev, vite build + vite preview (with server rendering), CSS and JS from taisho generate, CSS and JS from the package, the taisho() plugin, and client navigation between pages

Astro

Install the package and run npx taisho init and npx taisho generate. Astro bundles whatever is imported, so the CSS and the JS in the taisho/ folder come in through import in the layout (the relative path depends on where the file lives). The content that init writes already includes .astro files.

src/layouts/Base.astro
  • Generate before starting. The taisho/ folder has to exist before astro dev and astro build: run taisho generate first, or taisho watch in another terminal while developing. The alternative that was also tested is the Vite plugin in the Astro config, which writes the folder when the server and the build start.
  • Client navigation. With <ClientRouter /> (view transitions) nothing else is needed: the components on the new page work, also when going back.
  • The JS from the package. Importing @taishods/core/core instead of the generated file also works (on that path the CSS is the package’s, not your brand’s).
  • Node. Astro 7 requires Node 22.23.4 or newer, higher than the Core’s 22.18.
  • Astro 6 in development. With an empty Vite cache, the console can show 504 “Outdated Optimize Dep” errors, from Astro’s dev toolbar and from <ClientRouter />; they reproduce in an Astro 6 project without Core. The toolbar is turned off with devToolbar: { enabled: false } and, if the JS is imported from the package, the warning is avoided by declaring it in vite.optimizeDeps.include.
astro.config.mjs

Next (App Router)

The first steps are the same (init and generate; the content from init already includes .jsx and .tsx). The CSS is imported in the root layout, which is a server component. The JS touches document when it loads, so it’s loaded from a client component, inside an effect, which runs only in the browser and after hydration. Core initializes itself and uses event delegation.

app/layout.jsx
app/carga-taisho.jsx
  • Other ways to load the JS. The same battery passed with a dynamic import of @taishods/core/core inside the effect and with a static import of the generated file at the top of a client component: when prerendering on the server, Core doesn’t fail on evaluation.
  • Hydration. No hydration warning showed up in the console, with the three ways, in development and in production.
  • Client navigation. With Next’s <Link>, Core initializes the components on the new page with nothing else to do, also when going back.
  • data-scroll-behavior on <html>. Core’s reset sets scroll-behavior: smooth on <html> and, in next dev, Next 16 warns in the console until data-scroll-behavior="smooth" is added to that tag (as in the layout above).
  • Markup in JSX. Classes go in className. commandfor is written in lowercase, because React 19.3.1 doesn’t recognize commandFor and warns in the console; closedby is lowercase too. On the Select, defaultValue was used on the <select>.
  • Classes in JSX. taisho generate finds the classes written in className in the .jsx files: the resulting CSS includes the Modal’s and the Select’s. taisho check went over the test project’s files with no warnings.

SvelteKit

The first steps are the same (init and generate; the content from init already includes .svelte). The CSS is imported in the root layout. The JS touches document when it loads, so it’s imported inside onMount, which runs only in the browser. Core initializes itself and uses event delegation, so it serves the pages navigated to afterwards.

src/routes/+layout.svelte
  • Other ways to load the JS. The dynamic import of @taishods/core/core (with the package’s CSS) and the static import of the generated file in the layout header also passed the same battery: when rendering on the server, Core doesn’t fail while being evaluated.
  • Markup. The Modal and the Select were written with {@html}, exactly as each component’s documentation shows them.
  • Configuration. SvelteKit 3 expects its configuration inside the plugin (sveltekit({ adapter })) and no longer reads svelte.config.js.

What wasn’t tested

These cases weren’t tested and aren’t claimed to work:

  • Any other framework or meta-framework (Vue, Nuxt, Remix, React without Next, Qwik, SolidStart…).
  • SvelteKit with an adapter other than adapter-node, with prerendered pages, or with versions before 3.
  • Astro with React, Vue, or Svelte islands (client:*), with server rendering, or with an adapter; only static output was tested.
  • Next with the Pages Router, with webpack instead of Turbopack, with output: 'export', with dynamic server rendering, or with next/script.
  • Markup that the framework controls with its own state (for example, a hidden or an aria-expanded that the component updates): Core writes those attributes in the DOM, and whether that clashes with the framework wasn’t tested. Only fixed attributes were tested.
  • The other components: the test opens the Modal and the Select, nothing else.
  • Real Safari on iOS and screen readers (see Accessibility). The CDN quick start is tested in WebKit with an iPhone emulated by Playwright, which isn’t a real iPhone.

Web platform features

TaishoDS uses modern CSS and HTML APIs where they help (less JS, better accessibility), and each one degrades gracefully. In a current evergreen browser everything runs on the native path; in an older one, on the fallback.

Web platform Where it’s used If the browser doesn’t have it
CSS anchor positioningOverlay positioning (Popover, Menu, Tooltip, …)JS fallback (floating.ts)
Popover APITop layer for Popover / MenuFalls back to manual positioning
<dialog>Modal, Drawer, AlertDialogNative in every modern browser
Invoker commandsOpen/close Modal and Drawer without JSThe behavior JS runs the commands on the dialog when the browser does not ship them (Safari before 26.2, Firefox before 144)

The Core commits to Baseline widely available: what has worked in Chrome, Edge, Firefox, and Safari for about 30 months. Today that is Chrome and Edge 124, Firefox 125, and Safari 17.4 (iOS included), per the data of November 10, 2026; the floor is updated with every release. Internet Explorer and older browsers aren’t targeted. Whatever goes above that floor is in the table with its fallback or with what it loses if it’s missing: a browser at the floor loses the native detail (a transition, a positioning mode), not the feature, according to the CSS compatibility check; it wasn’t tested in browsers of that version.


Accessibility and motion

Components respect prefers-reduced-motion (animations are turned off or become instant), and each one is tested with axe. Details in Motion and Accessibility.