hyperfixi and _hyperscript

The hyperscript language was created by the
_hyperscript project, and that remains its home.
hyperfixi is not a competing language and is not positioned against
_hyperscript — we work in the same hypermedia ecosystem, on the same idea:
UI behavior that reads like a description of what it does.

hyperfixi is a different build of that idea: the same syntax and
semantics, packaged as a modular, tree-shakeable runtime.

When _hyperscript fits

If _hyperscript serves you well, keep using it. It is the canonical
implementation: one script tag, no toolchain, mature, and maintained by the
people who designed the language. For most sites that want hyperscript, it
is the obvious choice.

When hyperfixi fits

hyperfixi exists for situations where the packaging matters:

• Bundle size. Instead of one full-featured script, hyperfixi ships a
  ladder of builds — from a 5KB lite bundle to the complete hybrid runtime —
  and tree-shakes when imported through a bundler. See
  bundles for sizes and what each includes.
• npm-native tooling. Scoped @hyperfixi/* packages, TypeScript types,
  a Vite plugin, a language server, and a
  VS Code extension.
• Multilingual authoring. The LokaScript layer
  runs on hyperfixi, so hyperscript can be written in 24 languages.
• Extensions. hyperfixi adds features beyond the upstream language —
  reactive globals ($count), live blocks, component definitions, and a
  service-worker DSL. These are not standard hyperscript: code using
  them is not portable back to _hyperscript. They're catalogued under the
  hyperfixi-extensions and reactivity categories in the
  Pattern Browser so you always know which side of the line a
  pattern is on.

Compatibility

hyperfixi parses and runs standard hyperscript syntax. Our
164-pattern reference library is the working test bed: every
pattern on this site renders and executes through hyperfixi in your browser,
and we're not aware of a hyperscript pattern hyperfixi can't handle.
Per-pattern engine verification is tracked in the corpus (visible in the
Pattern Browser's engine filter) and is ongoing. If you find hyperscript
code that behaves differently on hyperfixi,
that's a bug — please report it.