Kudzu 0.7.2 - React hook normalization

Kudzu 0.7.2 accepts more ordinary React/Vite hook syntax while preserving static HTML and capability-only JavaScript.

New in 0.7.2

• Aliased supported React hooks normalize to canonical Kudzu hooks.
• Direct members such as React.useState(...) compile without loading React.
• Inline useCallback wrappers lower to existing handler specialization.
• Unsupported members, indirect hook references, stale captured-state dependencies, and effectful dependency expressions fail with source locations.
• Type-only React namespaces remain outside runtime migration validation.
• A React/Vite-shaped fixture verifies browser interaction and a zero-JavaScript static route.

Boundary

useCallback requires an inline function and a literal array containing only identifiers or primitive literals. memo, useMemo, React classes, indirect hook references, side-effect React imports, and dynamic React imports remain unsupported. React, a VDOM, hydration, and a retained browser component tree are not emitted.

Upgrade

npm install @kudzujs/core@^0.7.2

Kudzu 0.7.1 - Vite-style landing assets

Kudzu 0.7.1 lets ordinary React/Vite landing-page source retain common local stylesheet and static asset imports while preserving static HTML output and capability-only JavaScript.

New in 0.7.1

• Relative side-effect CSS imports are validated and erased before server module evaluation.
• Default CSS Module imports compile to deterministic scoped class maps with no client runtime.
• Relative image, SVG, and font imports compile to base-aware URL strings; supported assets also accept ?url.
• Relative CSS url(...) references are rewritten to base-aware emitted URLs while preserving query and hash suffixes.
• Static assets and CSS Modules work inside specialized relative keyed-row components.
• Declaration files under src are excluded from executable module compilation.
• Static migration routes continue to ship zero JavaScript.

Boundary

CSS Module composes, arbitrary import queries, import hashes or attributes, and named or namespace asset bindings remain unsupported. React, a VDOM, hydration, and a retained browser component tree are not emitted.

Upgrade

npm install @kudzujs/core@^0.7.1

Kudzu 0.7.0 - React-source migration preview

Kudzu Releases

0.7.0 - React-source migration preview

Kudzu 0.7.0 begins the migration track for ordinary React-shaped landing pages. Existing source may retain conventional supported imports from react; Kudzu rewrites those imports to compile-time APIs, pre-renders complete HTML, and emits only the route capabilities that are actually used. React, a virtual DOM, hydration, and a browser component tree are never emitted or executed.

import React, { useState } from "react"

export default function Header() {
  const [open, setOpen] = useState(false)

  return <React.Fragment>
    <button onClick={() => setOpen(!open)}>{open ? "Close" : "Menu"}</button>
    {open && <nav>Navigation</nav>}
  </React.Fragment>
}

New in 0.7.0

• Conventional unaliased named imports of supported hooks from react compile through Kudzu without loading React.
• Default, namespace, and named Fragment imports are accepted for migration source.
• Relative function components, props, children, conditions, attributes, text, and event handlers keep their familiar TSX shape.
• Static routes using the accepted React import forms still ship zero JavaScript.
• Interactive routes ship direct DOM capabilities only; the landing-page acceptance fixture adds state, text, attribute, condition, and menu-handler capabilities.
• Emitted modules are checked for surviving runtime React references, and side-effect React imports fail with a source location.
• Keyed collections now support analyzable filter, direct-property flatMap, Array.from, positional keys, recursively deep sibling child maps, nested conditions, latest-item handlers, multiple serializable row states, effects, and null object refs.

Current boundary

This is source migration support, not a React compatibility runtime. Aliased hooks, member hook calls such as React.useState, memo, useMemo, useCallback, React classes, React Router, Next-specific components, React UI packages, side-effect imports, and dynamic React imports remain unsupported. Migrate a real route, reduce the first unsupported pattern to a fixture, and extend the compiler one proven blocker at a time.

Measured fixture

The two-route landing fixture retains React imports across relative components. Its static route has no script, while its interactive mobile-menu route emits 10,245 B raw / 5,030 B aggregate gzip JavaScript across seven capability files. Seven clean builds after one warm-up measured a 310.0 ms median on the development machine described in MIGRATION_ROADMAP.md.

Upgrade

npm install @kudzujs/core@^0.7.0

New Kudzu source should continue importing APIs from @kudzujs/core. Retaining react imports is intended for migration input where minimizing source edits matters.