Evolution & Stability

Version Strategy & "src's Highest Version"

How json-to-dom-datalist evolves across revisions without breaking existing projects, and how npx json-to-dom-datalist dynamically selects the highest version.

Version Timeline

v1: Initial HTML5 datalist renderer proof-of-concept.
v2 (Current Highest): Decoupled modular architecture with DataListStore, frequency counting in groupBy, dynamic update() lifecycle, and universal globalThis compatibility for Node.js and browsers.

Developer's Guide: No Hardcoded Versions

Consumer application code should never import specific versions directly:

// Recommended: loads src's highest version automatically
import { DataList } from "json-to-dom-datalist";

// Or when copied via CLI:
import { DataList } from "./json-to-dom-datalist/index.js";

Instant Scaffolding via NPX CLI

The CLI discovers and copies the latest engine version without requiring manual configuration:

# Automatically picks the highest version (v2)
npx json-to-dom-datalist

# Or optionally specify destination folder and version target
npx json-to-dom-datalist ./src/components/datalist --version-target=v2

← Architecture Tasks & Roadmap →