GitHub - iDev-Games/State-JS: State.js is a CSS‑reactive framework that makes UI state and updates flow through CSS instead of JavaScript logic.

State.js is a CSS‑reactive framework that makes UI state and updates flow through CSS instead of JavaScript logic, enabling data‑driven animations and reactive UIs. Build dynamic, interactive interfaces using pure CSS and HTML.

License

What is State.js?

State.js is a super simple, efficient and lightweight CSS framework that exposes DOM element states as CSS variables. Track data attributes, form inputs, media playback, and element visibility - all automatically exposed for use in your CSS animations and transitions.

A CSS-first approach to reactive interfaces.

Using nothing but CSS, HTML and State.js, you can create:

📊 Dynamic dashboards and data visualizations
🎯 Interactive web applications with writing only CSS
🎨 Data-driven animations in CSS
🎮 Complex UIs (including game interfaces, health bars, score systems)

State.js is really lightweight and created with vanilla JavaScript without requiring any dependencies. Perfect for CSS-first development and reactive UI patterns!

Installation

Via NPM

npm i @idevgames/state-js

Via CDN

<script src="https://cdn.jsdelivr.net/npm/@idevgames/state-js/src/state.js"></script>

Download Directly

Download state.js and include it in your project:

<script src="/js/state.js"></script>

Quick Start

1. Basic Element Visibility Tracking

State.js automatically tracks when elements become visible:

<div class="fadeIn" data-state></div>

.fadeIn {
    opacity: 0;
}

.fadeIn.state {
    animation: fadeIn 1s forwards ease-in-out;
}

@keyframes fadeIn {
    0% { opacity: 0; }
    100% { opacity: 1; }
}

2. Data Attribute Tracking (Progress Bars & Meters)

Watch data attributes and expose them as CSS variables. Here's an example using a health bar (perfect for games, but works for any progress indicator):

<div id="player"
     data-state
     data-state-watch="health,score"
     data-state-var="true"
     data-health="100"
     data-health-min="0"
     data-health-max="100"
     data-score="0">

    <div class="health-bar"></div>
</div>

#player .health-bar {
    width: var(--state-health-percent);
    background: linear-gradient(90deg, red 0%, yellow 50%, green 100%);
}

/* Automatically triggered animations */
[data-health="0"] {
    animation: death 2s forwards;
}

[data-health="10"],
[data-health="20"],
[data-health="30"] {
    animation: pulse-red 1s infinite;
}

Update the state by simply changing the data attribute:

// Change health (State.js watches and updates CSS vars automatically)
document.getElementById('player').setAttribute('data-health', '75');

3. Form Input Tracking with Auto-Binding

No JavaScript needed! Automatically bind form inputs to update other elements:

<!-- Input automatically updates the healthBar element -->
<input type="range"
       id="healthSlider"
       data-state
       data-state-bind="healthBar"
       data-state-attr="health"
       min="0"
       max="100"
       value="75">

<!-- This element auto-updates when slider changes -->
<div id="healthBar"
     data-state
     data-state-watch="health"
     data-health="75">

    <div class="bar" style="width: var(--state-health-percent)"></div>
    <span data-state-display="health">75</span>
</div>

Bind to multiple elements (comma-separated):

<input data-state-bind="player,enemyHealthBar,scoreDisplay" data-state-attr="health">

4. Button Triggers (No JavaScript!)

Make any element clickable to control state:

<!-- Player with power-up state -->
<div id="player"
     data-state
     data-state-toggles="powered"
     data-powered="false">
    Player Character
</div>

<!-- Button that toggles the power-up on/off -->
<button data-state
        data-state-trigger
        data-state-bind="player"
        data-state-toggle="powered">
    Toggle Power-Up
</button>

<!-- Button that sets health to a specific value -->
<button data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="health"
        data-state-value="100">
    Full Health
</button>

<!-- Button that increments score by 10 (perfect for clickers!) -->
<button data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="score"
        data-state-increment="10">
    Add 10 Points
</button>

Trigger Modes:

Toggle: data-state-toggle="attribute" - Flips between true/false
Set: data-state-attr="attribute" + data-state-value="value" - Sets specific value
Increment: data-state-attr="attribute" + data-state-increment="amount" - Adds to current value
Decrement: data-state-attr="attribute" + data-state-decrement="amount" - Subtracts from current value

Advanced: Dynamic Calculations

Both increment and decrement support calc() expressions with CSS variables:

<!-- Static increment -->
<button data-state-increment="10">Add 10</button>

<!-- Dynamic: increment scales with level -->
<button data-state-increment="calc(var(--state-level) * 5)">
    Level-scaled Click
</button>

<!-- Dynamic: cost increases with score -->
<button data-state-increment="calc(1 + var(--state-score) * 0.1)">
    Increasing Returns
</button>

Both increment and decrement automatically respect data-[attr]-min and data-[attr]-max bounds!

Conditional Triggers:

Use data-state-condition to only execute operations when a condition is met (perfect for costs, requirements, unlock systems):

<!-- Only works if score >= 20 -->
<button data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="level"
        data-state-increment="1"
        data-state-condition="score >= 20">
    Level Up (costs 20)
</button>

<!-- Complex conditions with AND/OR -->
<button data-state-condition="gold >= 100 and level < 10">
    Affordable Upgrade
</button>

<!-- Multiple attributes -->
<button data-state-condition="health > 0 and mana >= 50">
    Cast Spell
</button>

When a condition fails, the button gets the state-disabled class automatically! Style it with CSS:

.state-disabled {
    opacity: 0.5;
    cursor: not-allowed;
    pointer-events: none;
}

Chaining Multiple Operations:

Use data-state-trigger-chain to perform multiple operations sequentially (perfect for complex game mechanics):

<!-- Level up button that both spends gold AND increases level -->
<button data-state
        data-state-trigger
        data-state-bind="player"
        data-state-condition="gold >= 100"
        data-state-trigger-chain="spendGold,gainLevel">
    Level Up (costs 100 gold)
</button>

<!-- Hidden trigger: deduct gold -->
<button id="spendGold"
        data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="gold"
        data-state-decrement="100"
        style="display:none">
</button>

<!-- Hidden trigger: add level -->
<button id="gainLevel"
        data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="level"
        data-state-increment="1"
        style="display:none">
</button>

Auto-firing Triggers:

Use data-state-autofire="true" to automatically fire a trigger whenever its condition becomes true (perfect for passive income, auto-unlocks, achievements, and automatic progression):

<!-- Passive income: auto-collect gold whenever it reaches 10 -->
<button id="autoCollect"
        data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="gold"
        data-state-decrement="10"
        data-state-condition="gold >= 10"
        data-state-autofire="true"
        data-state-trigger-chain="addScore"
        style="display:none">
</button>

<button id="addScore"
        data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="score"
        data-state-increment="10"
        style="display:none">
</button>

<!-- Auto-unlock: automatically upgrade when level reaches 5 -->
<button data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="upgraded"
        data-state-set="true"
        data-state-condition="level >= 5"
        data-state-autofire="true"
        style="display:none">
</button>

<!-- Achievement system: auto-trigger when condition met -->
<button data-state
        data-state-trigger
        data-state-bind="achievements"
        data-state-attr="firstWin"
        data-state-set="true"
        data-state-condition="wins >= 1"
        data-state-autofire="true"
        style="display:none">
</button>

The magic: When the condition transitions from false → true, the trigger fires automatically! No click required. No visibility required. This is the missing primitive for automatic game mechanics.

Works with any element:

<div data-state-trigger data-state-bind="player" data-state-toggle="shielded">
    Click me to toggle shield!
</div>

New in v1.1.0: Seven Game Development Extensions

State.js v1.1.0 adds seven powerful declarative primitives specifically designed for game development and interactive experiences. Build complete games with zero hand-written JavaScript logic.

1. data-state-interval — Repeating Timer Triggers

Automatically fire triggers at regular intervals (perfect for passive income, cooldowns, game ticks):

<!-- Passive gold income: +1 gold every second -->
<button id="passiveGold"
        data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="gold"
        data-state-increment="1"
        data-state-interval="1000"
        style="display:none">
</button>

<!-- Health regeneration: +5 HP every 2 seconds (only if alive) -->
<button data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="health"
        data-state-increment="5"
        data-state-interval="2000"
        data-state-condition="health > 0 and health < 100"
        style="display:none">
</button>

How it works:

Fires the trigger automatically every N milliseconds
Respects data-state-condition (won't fire if condition is false)
Uses a single efficient shared scheduler for all interval triggers
Perfect for idle games, passive effects, and time-based mechanics

2. data-state-set — Set Exact Value

Set an attribute to an exact value (unlike increment/decrement). Supports calc() expressions:

<!-- Reset health to full -->
<button data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="health"
        data-state-set="100">
    Full Heal
</button>

<!-- Set mana to half of max -->
<button data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="mana"
        data-state-set="calc(var(--state-manamax) / 2)">
    Restore 50% Mana
</button>

<!-- Level-scaled restore -->
<button data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="gold"
        data-state-set="calc(var(--state-level) * 100)">
    Set Gold to Level × 100
</button>

Use cases:

Reset/restore mechanics
Level-scaled rewards
Percentage-based calculations
Achievement unlocks (set boolean flags)

3. data-state-text — Template String Interpolation

Display dynamic text using {token} syntax that updates automatically:

<div id="player"
     data-state
     data-state-watch="level,health,healthmax,gold"
     data-level="1"
     data-health="100"
     data-healthmax="100"
     data-gold="0">
</div>

<!-- Text updates automatically when attributes change -->
<h1 data-state
    data-state-bind="player"
    data-state-text="Level {level} Hero">
</h1>

<p data-state
   data-state-bind="player"
   data-state-text="HP: {health}/{healthmax}">
</p>

<div data-state
     data-state-bind="player"
     data-state-text="Gold: {gold} | Level: {level}">
</div>

<!-- Works with any attribute -->
<span data-state
      data-state-bind="player"
      data-state-text="You have {gold} gold coins!">
</span>

How it works:

Replaces {attributeName} tokens with current attribute values
Updates automatically when any referenced attribute changes
Supports multiple tokens in one template
No manual display element management required

4. data-state-class — Conditional CSS Classes

Dynamically add/remove CSS classes based on conditions:

<!-- Add 'critical' class when health is low -->
<div id="healthBar"
     data-state
     data-state-bind="player"
     data-state-class="critical"
     data-state-class-condition="health <= 20">
</div>

<!-- Multiple conditional classes using numbered suffixes -->
<div id="player"
     data-state
     data-state-bind="game"
     data-state-class="low-health"
     data-state-class-condition="health <= 30"
     data-state-class-2="powered-up"
     data-state-class-condition-2="powerup == true"
     data-state-class-3="max-level"
     data-state-class-condition-3="level >= 99">
</div>

<!-- Style the classes in CSS -->
<style>
.critical {
    animation: critical-pulse 0.5s infinite;
    border: 3px solid red;
}

.low-health {
    filter: hue-rotate(180deg);
}

.powered-up {
    box-shadow: 0 0 20px gold;
    animation: glow 1s infinite;
}

.max-level {
    background: linear-gradient(45deg, gold, orange);
}
</style>

Features:

Supports up to 10 class/condition pairs per element (use -2, -3, etc.)
Classes add/remove automatically when conditions change
Perfect for visual state feedback
Works with any CSS animations or effects

5. data-state-sound — Procedural Sound Effects

Play procedurally generated Web Audio sounds on trigger clicks (no audio files needed!):

<!-- Built-in sounds: click, levelup, buy, error, coin -->
<button data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="score"
        data-state-increment="1"
        data-state-sound="click">
    Click (+1 score)
</button>

<button data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="level"
        data-state-increment="1"
        data-state-sound="levelup"
        data-state-condition="xp >= 100">
    Level Up!
</button>

<button data-state
        data-state-trigger
        data-state-bind="shop"
        data-state-attr="gold"
        data-state-decrement="50"
        data-state-sound="buy"
        data-state-condition="gold >= 50">
    Buy Item (50g)
</button>

<!-- Error sound when clicking disabled buttons -->
<button data-state
        data-state-trigger
        data-state-sound="error"
        data-state-condition="gold >= 1000">
    Expensive Item (1000g)
</button>

<!-- Coin pickup sound -->
<button data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="gold"
        data-state-increment="10"
        data-state-sound="coin">
    Collect Gold
</button>

Built-in sounds:

click - 80ms sawtooth beep (UI feedback)
levelup - 3-note arpeggio C4→E4→G4 (achievements)
buy - 100ms sine tone at 600Hz (purchases)
error - 80ms square wave at 120Hz (failures)
coin - Rising pitch 880→1200Hz (pickups)

Features:

Zero external dependencies (uses Web Audio API)
Procedurally generated (no audio files to load)
Plays on trigger click before executing the action
Respects browser autoplay policies

6. data-state-persist — localStorage Save/Restore

Automatically save and restore state to localStorage:

<div id="gameState"
     data-state
     data-state-watch="level,gold,health,xp"
     data-state-persist="true"
     data-state-persist-key="my-game-save"
     data-level="1"
     data-gold="0"
     data-health="100"
     data-xp="0">
</div>

How it works:

Automatically loads saved state on page load
Saves changes to localStorage with 500ms debounce (prevents excessive writes)
Saves all attributes listed in data-state-watch
Uses element ID as save key if data-state-persist-key not specified
Perfect for idle games, progress persistence, user preferences

Clear saved data:

// From browser console or your own JS:
localStorage.removeItem('my-game-save');

7. data-state-event — CustomEvent Dispatch

Dispatch CustomEvents when triggers fire (perfect for external integrations, analytics, achievements):

<!-- Dispatch event when score increases -->
<button data-state
        data-state-trigger
        data-state-bind="player"
        data-state-attr="score"
        data-state-increment="10"
        data-state-event="score-increased">
    +10 Score
</button>

<!-- Listen to events in JavaScript -->
<script>
document.addEventListener('state:score-increased', (e) => {
    console.log('Score changed!', e.detail);
    // e.detail contains:
    // {
    //   element: <the trigger button>,
    //   attr: "score",
    //   oldValue: "0",
    //   newValue: "10",
    //   boundId: "player"
    // }
});

// Track level-ups
document.addEventListener('state:level-up', (e) => {
    // Send to analytics
    gtag('event', 'level_up', { level: e.detail.newValue });
});

// Achievement tracking
document.addEventListener('state:achievement-unlocked', (e) => {
    showNotification(`Achievement unlocked: ${e.detail.attr}!`);
});
</script>

Use cases:

Analytics integration
Achievement systems
External UI updates
Debug logging
Third-party integrations

Event naming:

Event name is prefixed with state: (e.g., data-state-event="win" → state:win)
Events bubble up the DOM
Not cancelable (fire-and-forget)

Complete Game Example (All Declarative)

Combining all extensions, here's a complete idle clicker game:

<div id="game"
     data-state
     data-state-watch="gold,goldPerClick,goldPerSecond,level"
     data-state-persist="true"
     data-state-persist-key="idle-game-v1"
     data-gold="0"
     data-goldPerClick="1"
     data-goldPerSecond="0"
     data-level="1">

    <!-- Display with template interpolation -->
    <h1 data-state
        data-state-bind="game"
        data-state-text="Level {level} Miner">
    </h1>

    <p data-state
       data-state-bind="game"
       data-state-text="Gold: {gold} | Per Click: {goldPerClick} | Per Second: {goldPerSecond}">
    </p>

    <!-- Manual clicking -->
    <button data-state
            data-state-trigger
            data-state-bind="game"
            data-state-attr="gold"
            data-state-increment="calc(var(--state-goldPerClick))"
            data-state-sound="coin"
            data-state-event="gold-mined">
        Mine Gold
    </button>

    <!-- Upgrades with conditional classes -->
    <button id="upgradeClick"
            data-state
            data-state-trigger
            data-state-bind="game"
            data-state-trigger-chain="payUpgrade,addPower"
            data-state-condition="gold >= 50"
            data-state-sound="buy"
            data-state-class="affordable"
            data-state-class-condition="gold >= 50">
        Upgrade Pickaxe (50g)
    </button>

    <!-- Hidden triggers for upgrade chain -->
    <button id="payUpgrade"
            data-state-trigger
            data-state-bind="game"
            data-state-attr="gold"
            data-state-decrement="50"
            style="display:none">
    </button>

    <button id="addPower"
            data-state-trigger
            data-state-bind="game"
            data-state-attr="goldPerClick"
            data-state-increment="1"
            style="display:none">
    </button>

    <!-- Passive income with intervals -->
    <button data-state
            data-state-trigger
            data-state-bind="game"
            data-state-attr="gold"
            data-state-increment="calc(var(--state-goldPerSecond))"
            data-state-interval="1000"
            data-state-condition="goldPerSecond > 0"
            style="display:none">
    </button>

    <!-- Auto-level-up when gold reaches threshold -->
    <button data-state
            data-state-trigger
            data-state-bind="game"
            data-state-attr="level"
            data-state-increment="1"
            data-state-condition="gold >= 500"
            data-state-autofire="true"
            data-state-sound="levelup"
            data-state-event="level-up"
            style="display:none">
    </button>
</div>

<style>
/* Visual feedback with conditional classes */
.affordable {
    background: gold;
    animation: pulse 0.5s infinite;
}

#game[data-level="10"],
#game[data-level="25"],
#game[data-level="50"] {
    animation: milestone-celebration 1s ease-out;
}
</style>

This game has:

✅ Manual clicking with dynamic rewards
✅ Upgrade system with costs
✅ Passive income ticking every second
✅ Auto-level-up when reaching milestones
✅ Sound effects for all actions
✅ Visual feedback for affordability
✅ Persistent save/load with localStorage
✅ Event dispatch for analytics/achievements
✅ ZERO hand-written game logic JavaScript!

CSS Variables Created

State.js automatically creates CSS variables based on your configuration:

Visibility & Position

--state-visible (0 or 1)
--state-intersection (0-100%)
--state-viewport-x (0-100%)
--state-viewport-y (0-100%)

Watched Data Attributes

When using data-state-watch="health,score,level":

--state-health (raw value)
--state-health-percent (0-100%)
--state-health-normalized (0-1)
--state-health-deg (0-360deg)
--state-health-reverse (100%-0%)
--state-score (raw value)
--state-level (raw value)

Form Inputs

--state-value (current value)
--state-value-percent (percentage of range)
--state-min, --state-max (range bounds)

Media Elements

--state-time (current time)
--state-progress (0-100%)
--state-playing (0 or 1)
--state-volume (0-100)

Dimensions

--state-width (px)
--state-height (px)
--state-aspect-ratio (calculated)

Data Attributes API

Activation

<div data-state></div>
<!-- OR -->
<div class="enable-state"></div>

Configuration Attributes

Attribute	Description	Example
`data-state-var="true"`	Enable all CSS variables	`data-state-var="true"`
`data-state-watch="attr1,attr2"`	Watch specific data attributes	`data-state-watch="health,mana,xp"`
`data-state-bind="id1,id2"`	Auto-bind input to element IDs	`data-state-bind="player,enemy"`
`data-state-attr="attrName"`	Which attribute to update when binding	`data-state-attr="health"`
`data-state-value="value"`	Value to set when trigger is clicked (supports calc())	`data-state-value="100"` or `calc(var(--state-level) * 10)`
`data-state-increment="amount"`	Amount to add when trigger is clicked (supports calc(), respects min/max)	`data-state-increment="10"` or `calc(var(--state-level) * 5)`
`data-state-decrement="amount"`	Amount to subtract when trigger is clicked (supports calc(), respects min/max)	`data-state-decrement="5"` or `calc(var(--state-cost))`
`data-state-trigger`	Make element clickable to trigger state changes	`data-state-trigger`
`data-state-trigger-chain="id1,id2"`	Click other triggers sequentially after this one	`data-state-trigger-chain="payCost,addLevel"`
`data-state-condition="expression"`	Only execute if condition is true (adds `state-disabled` class when false)	`data-state-condition="score >= 20"` or `"gold >= 100 and level < 10"`
`data-state-autofire="true"`	Automatically fire trigger when condition becomes true (requires `data-state-condition`)	`data-state-autofire="true"`
`data-state-toggle="attrName"`	Toggle boolean attribute on/off when clicked	`data-state-toggle="powered"`
`data-state-display="attrName"`	Auto-display attribute value as text	`data-state-display="health"`
NEW v1.1.0	Game Development Extensions
`data-state-interval="ms"`	Auto-fire trigger every N milliseconds (respects conditions)	`data-state-interval="1000"`
`data-state-set="value"`	Set attribute to exact value (supports calc())	`data-state-set="100"` or `calc(var(--state-max))`
`data-state-text="template"`	Template string with expression support (v1.6.0: supports full expressions + string concat)	`data-state-text="{30 + (level - 1) * 10}hp"` or `"{health > 0 ? health + 'hp' : 'DEAD'}"`
`data-state-compute="expr"`	Computed attributes with expressions (v1.6.0: supports string concatenation)	`data-state-compute="label = hp + 'hp'; max = level * 100"`
`data-state-class="className"`	Conditional CSS class application	`data-state-class="critical"`
`data-state-class-condition="expr"`	Condition for class (use with data-state-class)	`data-state-class-condition="health <= 20"`
`data-state-sound="soundName"`	Play Web Audio sound on trigger (click, levelup, buy, error, coin)	`data-state-sound="coin"`
`data-state-persist="true"`	Auto-save/restore to localStorage	`data-state-persist="true"`
`data-state-persist-key="key"`	localStorage key (optional, defaults to element ID)	`data-state-persist-key="my-game"`
`data-state-event="eventName"`	Dispatch CustomEvent as "state:eventName"	`data-state-event="score-up"`
NEW v1.2.0	HTML Includes
`data-state-include="path"`	Fetch and inject HTML component from URL	`data-state-include="components/card.html"`
`data-state-toggles="attr1,attr2"`	Boolean state toggles	`data-state-toggles="active,locked"`
`data-state-dimensions="true"`	Track width/height	`data-state-dimensions="true"`
`data-state-media="true"`	Track media playback	`data-state-media="true"`
`data-state-global="true"`	Set CSS vars on `:root`	`data-state-global="true"`
`data-state-increment="10"`	Update increment for selectors	`data-state-increment="10"`
NEW v1.4.0	Event-Based Triggers
`data-state-trigger-on="eventName"`	Fire trigger on DOM event (default: "click")	`data-state-trigger-on="mouseenter"` or `"input"` or `"focus"`
`data-state-debounce="ms"`	Delay trigger execution until events stop (in milliseconds)	`data-state-debounce="500"`
`data-state-throttle="ms"`	Limit trigger firing rate (max once per N ms)	`data-state-throttle="200"`
NEW v1.5.0	Instance Management
`data-state-instantiate="id"`	Clone element by ID and insert into DOM	`data-state-instantiate="enemy-template"`
`data-state-remove="selector"`	Remove element(s) by ID or CSS selector	`data-state-remove=".enemy"`
`data-state-target="selector"`	Where to insert cloned element (default: body)	`data-state-target="#game"`
`data-state-insert="mode"`	Insert mode: append, prepend, before, after	`data-state-insert="prepend"`
`data-state-set-*="value"`	Override attribute on cloned element	`data-state-set-health="100"`
NEW v1.5.1	Random Number Generation
`data-state-random="max"`	Generate random number (1 to max, dice shorthand)	`data-state-random="6"`
`data-state-random="min,max"`	Generate random number (min to max, explicit range)	`data-state-random="0,100"`

Important Notes

Data Attribute Naming (HTML Requirement)

All data attributes must be lowercase. This is an HTML specification requirement, not a State.js limitation.

<!-- ✅ Correct: lowercase -->
<div data-state-watch="health,mana"></div>

<!-- ❌ Wrong: will be lowercased by browser -->
<div data-state-watch="Health,Mana"></div>  <!-- becomes "health,mana" -->

HTML automatically lowercases all attribute names. If you write data-myAttribute, the browser converts it to data-myattribute. State.js expects lowercase names throughout.

Trigger Chain Atomicity

Trigger chains are not transactional. If a link in the chain fails its condition, subsequent links still fire.

<!-- If link2 condition fails, link3 and link4 still execute -->
<button data-state-trigger
        data-state-trigger-chain="link1,link2,link3,link4">
</button>

This is intentional behavior. Each link in a chain is independent. If you need atomic transactions, use a single trigger with complex conditions instead of chains.

data-state-value: Numeric and Boolean Duality

data-state-value works on both numeric attributes AND boolean toggles. It writes the raw attribute directly, enabling idempotent state assignment (set to known state vs. blind toggle).

<!-- Numeric: Set exact value -->
<button data-state-trigger
        data-state-bind="player"
        data-state-attr="health"
        data-state-value="100">
  Reset Health
</button>

<!-- Boolean: Set to known state (not toggle) -->
<button data-state-trigger
        data-state-bind="modal"
        data-state-attr="open"
        data-state-value="false">
  Close Modal (idempotent - always closed)
</button>

Use data-state-toggle for flip behavior, data-state-value for assignment.

Autofire Edge Case

Autofire won't re-trigger if condition was already true at page load.

<!-- If enemyHp is already 0 on page load, this won't fire -->
<div data-state-trigger
     data-state-condition="enemyHp == 0"
     data-state-autofire="true"
     data-state-trigger-chain="showVictory">
</div>

Autofire detects when a condition becomes true (transitions from false→true). If the condition is already true at initialization, autofire won't trigger. Initialize your state values carefully to avoid this.

Instantiate: Beyond Game Attributes

data-state-set-* works for display content, not just game attributes. Use it to pass visual data (icons, labels, text) into templates.

<!-- Game attributes (common pattern) -->
<button data-state-instantiate="enemy"
        data-state-set-health="100"
        data-state-set-damage="20">
</button>

<!-- Display content (powerful, less obvious) -->
<button data-state-instantiate="achievement-card"
        data-state-set-icon="🏆"
        data-state-set-title="First Victory"
        data-state-set-description="Defeated your first enemy">
  Unlock Achievement
</button>

<!-- Template uses data-state-display to show values -->
<template id="achievement-card">
  <div class="card">
    <span data-state-display="icon"></span>
    <h3 data-state-display="title"></h3>
    <p data-state-display="description"></p>
  </div>
</template>

This unlocks template use cases beyond game mechanics - UI cards, notifications, dynamic lists, etc.

Per-State Configuration

<div data-state
     data-state-watch="health"
     data-health="100"
     data-health-min="0"
     data-health-max="100">
</div>

New in v1.2.0: HTML Includes

Build reusable, modular HTML components - just like any modern framework, but with zero build tools.

HTML Includes let you fetch and inject components declaratively. Create a component once, use it everywhere. Perfect for health bars, UI cards, player stats, inventory items, or any repeating UI pattern.

Basic Usage

<!-- From external file (cached after first load) -->
<div data-state-include="components/health-bar.html"></div>

<!-- From inline template (instant, zero latency) -->
<div data-state-include="#health-bar-template"></div>

<!-- Override component attributes -->
<div data-state-include="components/health-bar.html"
     id="player-health"
     data-hp="75"
     data-hp-max="150"></div>

<!-- Element tag doesn't matter, gets replaced -->
<i data-state-include="components/icon.html"></i>

Creating a Component

Option 1: External File (for modularity)

components/health-bar.html:

<div class="health-bar"
     data-state
     data-state-watch="hp"
     data-state-var="true"
     data-hp="100"
     data-hp-max="100">
    <div class="fill" style="width: var(--state-hp-percent); background: green; height: 20px;"></div>
    <span data-state-display="hp"></span>
</div>

Option 2: Inline Template (for performance)

<!-- Define template once in your HTML -->
<template id="health-bar-template">
    <div class="health-bar"
         data-state
         data-state-watch="hp"
         data-state-var="true"
         data-hp="100"
         data-hp-max="100">
        <div class="fill" style="width: var(--state-hp-percent); background: green; height: 20px;"></div>
        <span data-state-display="hp"></span>
    </div>
</template>

<!-- Use it anywhere (instant, no network request) -->
<div data-state-include="#health-bar-template" data-hp="75"></div>
<div data-state-include="#health-bar-template" data-hp="50"></div>
<div data-state-include="#health-bar-template" data-hp="100"></div>

How It Works

Template Mode (#id):

Clones from <template> tag or element by ID (instant, zero latency)
Merges attributes from include element to cloned component
Replaces include element with component
Initializes State.js on the injected component

Fetch Mode (path.html):

Fetches HTML from URL (cached after first load)
Merges attributes from include element to fetched component
Replaces include element with component
Initializes State.js on the injected component

All State.js features (triggers, persistence, intervals, sounds, etc.) work perfectly in included components!

Use Cases

Health/Mana Bars - Define once, use for player, enemies, NPCs
Inventory Items - Consistent item cards across inventory, shop, tooltip
UI Cards - Stat displays, achievement cards, notifications
Player Stats - Level, XP, gold displays
Navigation - Shared headers, footers, menus across pages

Configuration

Attribute	Description	Example
`data-state-include="path.html"`	Fetch and inject HTML from URL	`data-state-include="components/card.html"`
`data-state-include="#id"`	Clone from template or element by ID	`data-state-include="#card-template"`

Note: Any other attributes on the include element are copied to the injected component, allowing you to override default values.

Performance Strategy

Use templates (#id) for:

Critical, frequently-used components (zero latency)
Components needed immediately on page load
Single-page apps where all components fit in initial HTML

Use files (path.html) for:

Large component libraries (keeps HTML small)
Components used across multiple pages (modularity)
Production apps with proper HTTP caching

Local Development: File-based includes require HTTP/HTTPS (browser security prevents file:// fetching). Run any simple local server - Python's python -m http.server, Node's npx http-server, or VS Code Live Server. Template-based includes work anywhere, including file://!

Security Considerations

⚠️ Important: For security, external file fetches are disabled by default in State.js v1.4.2+.

Template-based includes are always safe and require no configuration:

<div data-state-include="#my-template"></div> <!-- ✅ Always works -->

To enable external file fetches:

// Only enable if you trust the source AND use HTTPS
state.allowExternalIncludes = true;

Security Best Practices:

Prefer templates over external files when possible
Use HTTPS only - never fetch over HTTP
Same-origin policy - fetch from your own domain
Content Security Policy - add CSP headers to your server
DOMPurify (optional) - for extra protection with external content:

<script src="https://cdn.jsdelivr.net/npm/dompurify@3/dist/purify.min.js"></script>
<script src="state.js"></script>
<script>
  // DOMPurify auto-detected and used if available
  state.allowExternalIncludes = true;
</script>

Attack Vectors to Avoid:

❌ User-controlled URLs: data-state-include="${userInput}"
❌ HTTP endpoints: data-state-include="http://..."
❌ Untrusted CDNs: data-state-include="https://random-cdn.com/..."
❌ Third-party domains without CORS/CSP protection

Why Template-Based Includes Are Secure: Templates (#id) are already in your HTML - if they're malicious, your page is already compromised. The security boundary is your deployment pipeline, not runtime injection.

New in v1.3.0: Computed State & Debug API

Computed State

Automatically calculate derived values from your data attributes - no manual updates needed!

Computed state keeps calculated values in sync with their dependencies. Perfect for health percentages, damage calculations, level-up requirements, or any derived game logic.

Basic Usage

<div id="player"
     data-state
     data-state-watch="hp,maxHp"
     data-state-compute="hpPercent = hp / maxHp * 100"
     data-hp="75"
     data-maxHp="100">

    <div class="health-bar" style="width: var(--state-hpPercent)%;"></div>
    <span>HP: <span data-state-display="hpPercent"></span>%</span>
</div>

Multiple Computations

Use semicolons to define multiple computed values:

<div data-state
     data-state-watch="hp,maxHp,level"
     data-state-compute="
         hpPercent = hp / maxHp * 100;
         isCritical = hp < 20;
         nextLevelXp = level * 100
     "
     data-hp="15"
     data-maxHp="100"
     data-level="5">
</div>

Supported Expressions

Math operators: +, -, *, /, %, ()
Comparisons: <, >, <=, >=, ==, !=
Logical operators: &&, ||, !
Ternary: condition ? valueA : valueB
Attribute references: Use attribute names directly (e.g., hp, maxHp)

Examples

<!-- Percentage calculation -->
<div data-state-compute="progress = completed / total * 100">

<!-- Ternary operator -->
<div data-state-compute="status = hp > 0 ? 'alive' : 'dead'">

<!-- Complex formula -->
<div data-state-compute="damage = (attack * 2) - defense">

<!-- Boolean check -->
<div data-state-compute="canLevelUp = xp >= level * 100">

<!-- Multiple dependencies -->
<div data-state-compute="totalStats = strength + agility + intelligence">
</div>

How It Works

Parse - State.js parses your compute expressions on setup
Auto-update - When any dependency changes, computed values recalculate automatically
Expose - Computed values become data-${name} attributes and --state-${name} CSS variables
Display - Use data-state-display to show computed values in your UI

Use Cases

Health/Mana percentages for progress bars
Damage calculations for combat systems
Level-up requirements (XP needed, stats gained)
Resource management (inventory space, currency conversions)
Status checks (isCritical, canAfford, isComplete)
Score calculations (combos, multipliers, totals)

Debug API

Console tools for inspecting and debugging reactive state - perfect for development and testing.

State.js provides a JavaScript API accessible via the browser console for debugging your application state.

State.inspectAll()

Returns an array of all reactive elements with their current state:

// In browser console
State.inspectAll()
/* Returns:
[
  {
    element: <div id="player">,
    id: "player",
    state: { hp: "75", maxHp: "100", hpPercent: "75" },
    config: { ... }
  },
  ...
]
*/

State.inspect(selector)

Inspect a specific element's state:

State.inspect('#player')
/* Returns:
{
  element: <div id="player">,
  id: "player",
  state: { hp: "75", maxHp: "100", hpPercent: "75" },
  config: { watchAttrs: ["hp", "maxHp"], ... }
}
*/

State.trace(attrName, enabled)

Enable/disable console logging for attribute changes:

// Enable tracing for HP changes
State.trace('hp', true)
// Now every time data-hp changes, you'll see:
// State.js [hp]: { element: <div>, id: "player", attribute: "hp", oldValue: "75", newValue: "65" }

// Disable tracing
State.trace('hp', false)

Usage Examples

// Debug all reactive elements
const elements = State.inspectAll()
console.table(elements.map(e => e.state))

// Check specific element state
const player = State.inspect('#player')
console.log('Player HP:', player.state.hp)

// Trace multiple attributes
State.trace('hp')
State.trace('gold')
State.trace('xp')
// Now see all changes to hp, gold, and xp in real-time

// Find elements with low HP
State.inspectAll()
  .filter(e => parseFloat(e.state.hp) < 20)
  .forEach(e => console.log(`${e.id} is critical!`))

Use Cases

Debugging - See all state changes in real-time
Testing - Verify attribute values during development
Optimization - Track which attributes update frequently
Learning - Understand how State.js works internally

New in v1.4.0: Event-Based Triggers

Fire triggers on ANY DOM event - not just clicks! Listen to hover, focus, input, scroll, and more with built-in debounce/throttle support.

Event-based triggers let you respond to any DOM event declaratively. Perfect for form interactions, hover effects, scroll tracking, visibility detection, and real-time input validation - all without writing JavaScript event listeners.

Basic Usage

Use data-state-trigger-on to specify which event should fire the trigger:

<!-- Default: click (backward compatible) -->
<button data-state-trigger
        data-state-bind="player"
        data-state-attr="score"
        data-state-increment="1">
    Click to score
</button>

<!-- Explicit click -->
<button data-state-trigger
        data-state-trigger-on="click"
        data-state-bind="player"
        data-state-attr="score"
        data-state-increment="1">
    Click to score
</button>

<!-- Hover to increment -->
<div data-state-trigger
     data-state-trigger-on="mouseenter"
     data-state-bind="stats"
     data-state-attr="hovers"
     data-state-increment="1">
    Hover over me!
</div>

<!-- Fire on focus -->
<input data-state-trigger
       data-state-trigger-on="focus"
       data-state-bind="form"
       data-state-attr="activeField"
       data-state-set="username">

<!-- Fire on form submission -->
<form data-state-trigger
      data-state-trigger-on="submit"
      data-state-bind="stats"
      data-state-attr="submits"
      data-state-increment="1">
    <!-- Form automatically prevents page reload -->
    <input type="text" name="username">
    <button type="submit">Submit</button>
</form>

Supported Events

Mouse Events:

click - Default trigger behavior
dblclick - Double-click
mouseenter - Mouse enters element
mouseleave - Mouse leaves element
mouseover - Mouse moves over element
mouseout - Mouse moves out of element

Form Events:

input - Text input, range slider changes (fires on every keystroke)
change - Select dropdowns, checkboxes, radio buttons (fires on blur/commit)
focus - Element gains focus
blur - Element loses focus
submit - Form submission (automatically calls preventDefault())

Keyboard Events:

keydown - Key is pressed down
keyup - Key is released
keypress - Key is pressed (deprecated but supported)

Scroll Events:

scroll - Element scrolls (use with throttle!)

Custom Events:

intersect - Element becomes visible (custom event from IntersectionObserver)
Any CustomEvent dispatched via JavaScript

Debounce (Delay After Rapid Events)

Use data-state-debounce to delay execution until events stop firing:

<!-- Search input: only fire 300ms after user stops typing -->
<input type="text"
       data-state-trigger
       data-state-trigger-on="input"
       data-state-debounce="300"
       data-state-bind="search"
       data-state-attr="query"
       data-state-increment="1">

<!-- Resize handler: only fire 500ms after window stops resizing -->
<div data-state-trigger
     data-state-trigger-on="resize"
     data-state-debounce="500"
     data-state-bind="layout"
     data-state-attr="width"
     data-state-set="calc(100)">
</div>

How debounce works:

Event fires (e.g., user types a character)
Timer starts counting down from specified ms
If another event fires before timer completes, reset the timer
When timer completes without interruption, execute trigger
Use for: Text input, resize, autocomplete, validation

Throttle (Limit Firing Rate)

Use data-state-throttle to limit how often a trigger can fire:

<!-- Scroll tracking: fire at most once per 200ms (5x/second max) -->
<div data-state-trigger
     data-state-trigger-on="scroll"
     data-state-throttle="200"
     data-state-bind="stats"
     data-state-attr="scrolls"
     data-state-increment="1"
     style="height: 200px; overflow-y: scroll;">
    <div style="height: 1000px;">Scroll content...</div>
</div>

<!-- Mouse tracking: limit to 100ms (10x/second max) -->
<div data-state-trigger
     data-state-trigger-on="mousemove"
     data-state-throttle="100"
     data-state-bind="cursor"
     data-state-attr="moves"
     data-state-increment="1">
    Track mouse movement
</div>

How throttle works:

Event fires and trigger executes immediately
Start cooldown timer for specified ms
Any events during cooldown are ignored
After cooldown completes, next event can fire
Use for: Scroll, mousemove, resize, frequent events

Debounce vs Throttle:

Debounce: Wait until activity stops → fires once at the end
Throttle: Fire regularly during activity → fires multiple times at limited rate

Visibility Detection

The intersect event fires when an element enters the viewport:

<!-- Track when user scrolls element into view -->
<div data-state-trigger
     data-state-trigger-on="intersect"
     data-state-bind="analytics"
     data-state-attr="views"
     data-state-increment="1">
    Content that tracks visibility
</div>

<!-- Lazy-load content -->
<div data-state-trigger
     data-state-trigger-on="intersect"
     data-state-bind="lazySection"
     data-state-attr="loaded"
     data-state-set="true">
    <!-- Fires once when scrolled into view -->
</div>

How it works:

State.js uses IntersectionObserver to track visibility
When element becomes visible for the first time, dispatches intersect CustomEvent
Trigger fires and can update state, trigger chains, play sounds, etc.
Use for: Analytics, lazy loading, scroll-triggered animations, achievement tracking

Form Auto-Submit Prevention

Form submit events automatically call preventDefault() to prevent page reload:

<form id="contactForm"
      data-state
      data-state-watch="submits"
      data-submits="0">

    <input type="text" name="email" required>

    <!-- Submit increments counter WITHOUT reloading page -->
    <button type="submit"
            data-state-trigger
            data-state-trigger-on="submit"
            data-state-bind="contactForm"
            data-state-attr="submits"
            data-state-increment="1"
            data-state-sound="buy"
            data-state-event="form-submitted">
        Submit
    </button>
</form>

<p>Submissions: <span data-state-display="submits">0</span></p>

No JavaScript required! The form won't reload the page - State.js handles it automatically.

Combining with Conditions

Event triggers respect data-state-condition just like click triggers:

<div id="game"
     data-state
     data-state-watch="gold,active"
     data-state-toggles="active"
     data-gold="0"
     data-active="false">

    <!-- Only track hovers when game is active -->
    <div data-state-trigger
         data-state-trigger-on="mouseenter"
         data-state-condition="active == true"
         data-state-bind="game"
         data-state-attr="gold"
         data-state-increment="1">
        Hover to collect gold (only when active)
    </div>

    <!-- Only track input when game is active -->
    <input data-state-trigger
           data-state-trigger-on="input"
           data-state-debounce="500"
           data-state-condition="active == true"
           data-state-bind="game"
           data-state-attr="gold"
           data-state-increment="5">
</div>

Result: Triggers are disabled (get state-disabled class) when condition is false, just like click triggers!

Real-World Examples

Live Search Counter

<div id="search"
     data-state
     data-state-watch="queries"
     data-queries="0">

    <!-- Debounced search: only counts after user stops typing -->
    <input type="text"
           placeholder="Search..."
           data-state-trigger
           data-state-trigger-on="input"
           data-state-debounce="500"
           data-state-bind="search"
           data-state-attr="queries"
           data-state-increment="1"
           data-state-event="search-query">

    <p>Searches performed: <span data-state-display="queries">0</span></p>
</div>

Scroll Progress Tracker

<div id="article"
     data-state
     data-state-watch="scrollEvents"
     data-scrollEvents="0">

    <div class="content"
         data-state-trigger
         data-state-trigger-on="scroll"
         data-state-throttle="200"
         data-state-bind="article"
         data-state-attr="scrollEvents"
         data-state-increment="1"
         style="height: 300px; overflow-y: scroll;">
        <div style="height: 2000px;">Long scrollable content...</div>
    </div>

    <p>Scroll events: <span data-state-display="scrollEvents">0</span></p>
</div>

Form Field Tracking

<div id="formTracking"
     data-state
     data-state-watch="focusCount,changes"
     data-focusCount="0"
     data-changes="0">

    <!-- Track focus -->
    <input type="text"
           placeholder="Username"
           data-state-trigger
           data-state-trigger-on="focus"
           data-state-bind="formTracking"
           data-state-attr="focusCount"
           data-state-increment="1">

    <!-- Track changes -->
    <select data-state-trigger
            data-state-trigger-on="change"
            data-state-bind="formTracking"
            data-state-attr="changes"
            data-state-increment="1">
        <option>Option 1</option>
        <option>Option 2</option>
    </select>

    <p>Fields focused: <span data-state-display="focusCount">0</span></p>
    <p>Changes made: <span data-state-display="changes">0</span></p>
</div>

Use Cases

Event-based triggers are perfect for:

📝 Live search/autocomplete (input + debounce)
📊 Analytics tracking (focus, scroll, visibility)
🎯 Hover effects and interactions (mouseenter/leave)
📋 Form validation and submission (submit, change, blur)
📜 Scroll progress indicators (scroll + throttle)
👀 Lazy loading and content reveal (intersect)
⌨️ Keyboard shortcut tracking (keydown/up)
🎮 Interactive games (mousemove, keypress)
📱 Mobile gesture tracking (with Touch.js integration)

Performance Tips

Always throttle scroll and mousemove events (100-200ms recommended)
Debounce text input for search/autocomplete (300-500ms recommended)
Use intersect for lazy loading instead of scroll events
Combine with conditions to disable triggers when not needed
Prefer change over input for dropdowns/checkboxes (fires less frequently)

Configuration

Attribute	Description	Example
`data-state-trigger-on="eventName"`	Which DOM event fires the trigger (default: "click")	`data-state-trigger-on="mouseenter"`
`data-state-debounce="ms"`	Delay trigger execution until events stop (in milliseconds)	`data-state-debounce="500"`
`data-state-throttle="ms"`	Limit trigger firing rate (max once per N milliseconds)	`data-state-throttle="200"`

Special behaviors:

submit events automatically call event.preventDefault()
intersect is a custom event fired by IntersectionObserver
click is the default if data-state-trigger-on is omitted
Triggers with trigger-on="click" still get cursor: pointer style

New in v1.5.0: Instance Management

Dynamically create and remove DOM elements using declarative triggers - perfect for spawning enemies, creating projectiles, managing inventory items, and building dynamic UI systems.

Basic Instantiation

Clone any element by ID and insert it into the DOM:

<!-- Spawn button -->
<button data-state-trigger
        data-state-instantiate="enemy-template"
        data-state-target="#game"
        data-state-insert="append">
  Spawn Enemy
</button>

<!-- Template element (hidden) -->
<div id="enemy-template" class="enemy" data-state>
  <!-- Your enemy content -->
</div>

What happens:

Clones #enemy-template element
Generates unique ID: enemy-template-1, enemy-template-2, etc.
Inserts into #game container
Automatically initializes State.js on the clone
Updates instance count on source element

Attribute Overrides

Customize each cloned instance with different attributes:

<button data-state-trigger
        data-state-instantiate="enemy-template"
        data-state-target="#game"
        data-state-set-health="100"
        data-state-set-type="goblin"
        data-state-set-level="5">
  Spawn Goblin (Lvl 5, 100 HP)
</button>

<button data-state-trigger
        data-state-instantiate="enemy-template"
        data-state-target="#game"
        data-state-set-health="200"
        data-state-set-type="orc"
        data-state-set-level="10">
  Spawn Orc (Lvl 10, 200 HP)
</button>

How attribute overrides work:

Use data-state-set-* to set attributes on cloned instances
Most attributes become data-* (e.g., data-state-set-health="100" → data-health="100")
Special case: data-state-set-class="enemy" sets the actual class attribute (not data-class)

Common use cases:

<!-- Set data attributes -->
<button data-state-instantiate="item"
        data-state-set-name="Sword"
        data-state-set-damage="50">
  <!-- Creates: data-name="Sword" data-damage="50" -->
</button>

<!-- Set CSS class for styling/removal -->
<button data-state-instantiate="enemy"
        data-state-set-class="monster goblin">
  <!-- Creates: class="monster goblin" -->
</button>

<!-- Combine both -->
<button data-state-instantiate="card"
        data-state-set-class="playing-card"
        data-state-set-suit="hearts"
        data-state-set-rank="ace">
  <!-- Creates: class="playing-card" data-suit="hearts" data-rank="ace" -->
</button>

Insert Modes

Control where the cloned element is inserted:

<!-- Append to end (default) -->
<button data-state-instantiate="item"
        data-state-target="#inventory"
        data-state-insert="append">Add Item (End)</button>

<!-- Prepend to beginning -->
<button data-state-instantiate="item"
        data-state-target="#inventory"
        data-state-insert="prepend">Add Item (Start)</button>

<!-- Insert before target -->
<button data-state-instantiate="notification"
        data-state-target="#top-bar"
        data-state-insert="before">Add Before</button>

<!-- Insert after target -->
<button data-state-instantiate="notification"
        data-state-target="#top-bar"
        data-state-insert="after">Add After</button>

Instance Counting

Source elements automatically track how many instances have been created:

<div id="enemy-template" data-state data-state-watch="enemy-templateCount">
  <!-- Template content -->
</div>

<p>Enemies spawned: <span data-state-display="enemy-templateCount">0</span></p>

Automatic counter attribute: data-{sourceId}Count is updated on the source element each time an instance is created.

Removing Elements

Remove elements by ID or CSS selector:

<!-- Remove by ID (single element) -->
<button data-state-trigger
        data-state-remove="enemy-template-1">
  Remove Enemy #1
</button>

<!-- Remove all matching selector -->
<button data-state-trigger
        data-state-remove=".enemy">
  Clear All Enemies
</button>

<!-- Remove by attribute -->
<button data-state-trigger
        data-state-remove="[data-type='goblin']">
  Remove All Goblins
</button>

How it works:

ID removal (no . or [): Removes single element by ID
Selector removal (starts with . or contains [): Removes all matching elements

Conditional Removal

Only remove elements that meet specific conditions:

<!-- Remove enemies with 0 HP -->
<button data-state-trigger
        data-state-remove=".enemy"
        data-state-condition="health <= 0">
  Remove Dead Enemies
</button>

<!-- Remove low-value items -->
<button data-state-trigger
        data-state-remove=".item"
        data-state-condition="value < 10">
  Sell Junk Items
</button>

Complete Example: Enemy Spawner

<div id="game">
  <!-- Spawn controls -->
  <button data-state-trigger
          data-state-instantiate="enemy"
          data-state-target="#battlefield"
          data-state-set-health="100"
          data-state-set-type="goblin">
    Spawn Goblin
  </button>

  <button data-state-trigger
          data-state-instantiate="enemy"
          data-state-target="#battlefield"
          data-state-set-health="200"
          data-state-set-type="orc">
    Spawn Orc
  </button>

  <!-- Cleanup controls -->
  <button data-state-trigger
          data-state-remove=".enemy"
          data-state-condition="health <= 0">
    Remove Dead
  </button>

  <button data-state-trigger
          data-state-remove=".enemy">
    Clear All
  </button>

  <!-- Instance counter -->
  <p>Total spawned: <span data-state-display="enemyCount">0</span></p>

  <!-- Battlefield container -->
  <div id="battlefield"></div>
</div>

<!-- Hidden template -->
<div id="enemy" class="enemy"
     data-state
     data-state-watch="health,type,enemyCount"
     data-health="100"
     data-type="enemy"
     style="display: none;">

  <h3><span data-state-display="type">Enemy</span></h3>
  <p>HP: <span data-state-display="health">100</span></p>

  <button data-state-trigger
          data-state-attr="health"
          data-state-increment="-25">
    Attack (-25 HP)
  </button>
</div>

Use Cases

Perfect for:

🎮 Game Development: Spawn enemies, projectiles, particles, loot drops
📦 Inventory Systems: Add/remove items, manage equipment slots
🃏 Card Games: Deal cards, shuffle decks, create hands
📝 Dynamic Forms: Add/remove form fields, repeating sections
🔔 Notifications: Create toast messages, alerts, popups
📊 Data Visualization: Generate chart elements, data points
🛒 Shopping Carts: Add/remove products, update quantities
💬 Chat Systems: Add messages, manage conversation threads

Security

Instance management uses DOMParser for secure element cloning (same as v1.4.2 HTML includes):

✅ No innerHTML usage
✅ Safe from XSS attacks
✅ CSP compliant
✅ Zero external dependencies

Reading Element Values at Instantiate Time (v1.6.1)

The final piece for pur declarative apps - Read values from form inputs or any element at trigger-time.

Use data-state-set-*-from to capture user input when cloning, enabling fully declarative forms without any JavaScript.

Basic Usage

<!-- Text input → clone -->
<input id="taskName" placeholder="Enter task name">
<button data-state-trigger
        data-state-instantiate="task-tpl"
        data-state-set-label-from="#taskName">
    Add Task
</button>

<!-- Template uses the captured value -->
<div id="task-tpl" data-state data-label="New task" style="display:none">
    <span data-state-display="label">New task</span>
</div>

How it works:

User types in #taskName input
Click triggers instantiate
State.js reads input.value at click-time
Sets data-label on the clone with the input's current value
Template displays the user's text - no JavaScript required!

Supported Elements

The -from attribute works with any element:

<input> - Reads .value property
<textarea> - Reads .value property
<select> - Reads .value property (selected option)
Contenteditable - Reads .textContent property
Any element - Falls back to .textContent

Multiple Inputs Example

<input id="expenseName" placeholder="Description">
<input id="expenseAmount" type="number" placeholder="Amount">
<select id="expenseCategory">
    <option value="food">Food</option>
    <option value="transport">Transport</option>
</select>

<button data-state-trigger
        data-state-instantiate="expense-tpl"
        data-state-set-label-from="#expenseName"
        data-state-set-amount-from="#expenseAmount"
        data-state-set-category-from="#expenseCategory">
    Add Expense
</button>

Complex Selectors

Full CSS selector support - not limited to IDs:

<!-- Class selector -->
<button data-state-set-value-from=".active-input">

<!-- Attribute selector -->
<button data-state-set-name-from="input[name='username']">

<!-- Complex selector -->
<button data-state-set-text-from=".form-active .description-field">

<!-- Descendant selector -->
<button data-state-set-content-from="#panel textarea">

Combining Static and Dynamic Values

You can combine static fallbacks with dynamic -from values:

<!-- If input is empty or not found, uses "Default Task" -->
<button data-state-set-label="Default Task"
        data-state-set-label-from="#taskInput">

Priority: -from takes precedence if the element is found and has a value.

Real-World Example: Budget Tracker

Before v1.6.1 (required JavaScript):

<input id="incomeName">
<button id="addBtn" data-state-instantiate="entry-tpl">Add</button>

<script>
// JS needed to read input value
addBtn.addEventListener('mousedown', () => {
    addBtn.setAttribute('data-state-set-label',
        document.getElementById('incomeName').value);
});
</script>

After v1.6.1 (fully declerative):

<input id="incomeName">
<button data-state-trigger
        data-state-instantiate="entry-tpl"
        data-state-set-label-from="#incomeName">
    Add
</button>

Result: The 15 lines of JavaScript are eliminated entirely. Pure declarative forms.

Contenteditable Support

Works with rich text editors:

<div contenteditable id="noteEditor">
    Type your <b>formatted</b> note here
</div>

<button data-state-trigger
        data-state-instantiate="note-tpl"
        data-state-set-content-from="#noteEditor">
    Save Note
</button>

Edge Cases

Element not found:

Treated as empty string
Instantiate continues normally
Clone gets empty value for that attribute

Empty input value:

Sets empty string on clone: data-label=""
Does not fall back to static value
-from always wins when element exists

Should State.js clear the input after adding?

No - that's a UX decision that varies by use case
Some apps clear (budget demo style)
Some apps keep value (edit mode style)
Use trigger chains to reset if needed: data-state-trigger-chain="addEntry,clearInput"

Configuration

Attribute	Description	Example
`data-state-instantiate="id"`	ID of element to clone	`data-state-instantiate="enemy"`
`data-state-remove="selector"`	ID or CSS selector of element(s) to remove	`data-state-remove=".enemy"`
`data-state-target="selector"`	Where to insert cloned element (default: body)	`data-state-target="#game"`
`data-state-insert="mode"`	Insert mode: append, prepend, before, after (default: append)	`data-state-insert="prepend"`
`data-state-set-*="value"`	Override attribute on cloned element (becomes `data-*`)	`data-state-set-health="100"` → `data-health="100"`
`data-state-set-class="value"`	Special: Sets actual `class` attribute (not `data-class`)	`data-state-set-class="enemy"` → `class="enemy"`
`data-state-condition="expr"`	Condition for removal (only with remove)	`data-state-condition="health <= 0"`

Auto-generated:

Unique IDs: {sourceId}-{counter} (e.g., enemy-1, enemy-2)
Instance count: data-{sourceId}Count on source element
Clones automatically have display: none removed if present on template

New in v1.5.1: Random Number Generation

Essential for game development - Generate random numbers declaratively using pure HTML attributes.

State.js provides simple, zero-dependency random number generation for:

🎲 Dice rolls
🎁 Loot drops
⚔️ Damage calculation
🎰 Probability systems
🎮 Procedural generation

Basic Usage

<!-- Dice shorthand: 1-6 -->
<button data-state-trigger
        data-state-bind="player"
        data-state-attr="damage"
        data-state-random="6">
  Roll 1d6 Damage
</button>

<!-- Explicit range: 0-100 -->
<button data-state-trigger
        data-state-bind="loot"
        data-state-attr="rarity"
        data-state-random="0,100">
  Roll Loot Rarity
</button>

<!-- Any range: 10-20 -->
<button data-state-trigger
        data-state-bind="enemy"
        data-state-attr="health"
        data-state-random="10,20">
  Spawn with Random HP
</button>

Syntax Options

Dice shorthand (1 to N):

data-state-random="6"     <!-- 1-6 (common d6) -->
data-state-random="20"    <!-- 1-20 (common d20) -->
data-state-random="100"   <!-- 1-100 (percentile) -->

Explicit range (min to max):

data-state-random="1,6"    <!-- 1-6 (explicit) -->
data-state-random="0,100"  <!-- 0-100 (percentage) -->
data-state-random="10,50"  <!-- 10-50 (custom range) -->

Advanced Patterns

Random with conditions:

<!-- Only roll if player has attempts left -->
<button data-state-trigger
        data-state-bind="player"
        data-state-attr="reward"
        data-state-random="1,100"
        data-state-condition="attempts > 0">
  Try Your Luck
</button>

Random with trigger chains:

<!-- Roll damage, then apply to enemy -->
<button data-state-trigger
        data-state-bind="combat"
        data-state-attr="damage"
        data-state-random="1,6"
        data-state-trigger-chain="applyDamage">
  Attack
</button>

<div id="applyDamage"
     data-state-trigger
     data-state-bind="enemy"
     data-state-attr="health"
     data-state-decrement="calc(var(--state-damage))"></div>

Random intervals:

<!-- Random event every 5 seconds -->
<div data-state-trigger
     data-state-interval="5000"
     data-state-bind="game"
     data-state-attr="event"
     data-state-random="1,10">
</div>

Random with instantiate:

<!-- Spawn enemy with random health -->
<button data-state-trigger
        data-state-instantiate="enemy-template"
        data-state-attr="health"
        data-state-random="50,100"
        data-state-set-health="calc(var(--state-health))">
  Spawn Random Enemy
</button>

Configuration

Attribute	Description	Example
`data-state-random="max"`	Dice shorthand: 1 to max	`data-state-random="6"` → 1-6
`data-state-random="min,max"`	Explicit range: min to max	`data-state-random="0,100"` → 0-100

Requirements:

Must have data-state-trigger attribute
Must specify data-state-attr (which attribute to set)
Must have data-state-bind or be inside [data-state] element
Uses native Math.random() - zero dependencies

How it works:

When trigger fires, checks for data-state-random
Parses range (single number = dice shorthand, two numbers = explicit)
Generates random integer in range using Math.floor(Math.random() * (max - min + 1)) + min
Sets the attribute value to the random number
Works seamlessly with conditions, chains, intervals, and all other State.js features

New in v1.6.0: Expression-Based Templates

Templating without leaving HTML - Computed values, string concatenation, and conditional logic in pure declarative attributes.

CSS has fundamental limitations - you cannot use calc() in the content property, and you cannot concatenate strings from custom properties. State.js v1.6.0 solves this with expression-based templates.

The Problem (Before v1.6.0)

/* This doesn't work in CSS! */
.enemy-label:after {
  --hp: calc(30 + (var(--state-level) - 1) * 10);
  content: var(--hp) "hp";  /* Can't concatenate! */
}

The Solution (v1.6.0)

<!-- Simple: Computed value + string -->
<span data-state-text="{30 + (level - 1) * 10}hp">30hp</span>

<!-- Conditional: Ternary operator -->
<span data-state-text="{health > 0 ? health + 'hp' : 'DEAD'}">100hp</span>

<!-- Complex: Multiple expressions -->
<span data-state-text="Level {level} - {xp}/{xpMax} XP">Level 5 - 750/1000 XP</span>

Basic Usage

Simple attribute display (still works):

<span data-state-text="HP: {health}">HP: 100</span>

String concatenation:

<span data-state-text="{health}hp">100hp</span>
<span data-state-text="{gold} gold">500 gold</span>

Computed numeric expressions:

<!-- Enemy HP scales with player level -->
<span data-state-text="{30 + (level - 1) * 10}hp">30hp</span>

<!-- Damage range -->
<span data-state-text="{minDmg + '-' + maxDmg}">10-15</span>

<!-- Percentage -->
<span data-state-text="{health / maxHealth * 100}%">75%</span>

Conditional display with ternary:

<!-- Show different text based on condition -->
<span data-state-text="{health > 0 ? health + 'hp' : 'DEAD'}">100hp</span>

<!-- Loot rarity -->
<span data-state-text="{rarity >= 75 ? 'Legendary' : rarity >= 25 ? 'Rare' : 'Common'}">Common</span>

<!-- Status indicator -->
<span data-state-text="{active ? 'Online' : 'Offline'}">Online</span>

Multiple expressions in one template:

<span data-state-text="Level {level} Hero">Level 5 Hero</span>
<span data-state-text="{name} - {health}/{maxHealth}hp">Warrior - 75/100hp</span>
<span data-state-text="XP: {xp}/{xpMax} ({xp / xpMax * 100}%)">XP: 750/1000 (75%)</span>

Advanced Patterns

Nested expressions:

<span data-state-text="{level > 10 ? 'Veteran (' + level + ')' : 'Novice'}">Novice</span>

Math operations:

<span data-state-text="{health + shield}hp total">{health + shield}hp total</span>
<span data-state-text="DPS: {damage * attackSpeed}">DPS: 45</span>

Logical operations:

<span data-state-text="{gold >= 100 and level >= 5 ? 'Can Buy' : 'Locked'}">Locked</span>

String Concatenation in Computed State

v1.6.0 also adds string concatenation to data-state-compute:

<div data-state
     data-state-watch="hp,level"
     data-state-compute="
       enemyHp = 30 + (level - 1) * 10;
       hpLabel = enemyHp + 'hp';
       status = hp > 0 ? 'Alive' : 'Dead'
     ">
  <span data-state-display="hpLabel">30hp</span>
  <span data-state-display="status">Alive</span>
</div>

Compute creates attributes, then display them:

Computation result stored as data-hpLabel="30hp"
Can be used in CSS, displayed with data-state-display, or referenced elsewhere
Reusable across multiple elements

Expression Syntax Reference

Operators supported:

Arithmetic: +, -, *, /
Comparison: ==, !=, <, >, <=, >=
Logical: and/&&, or/||, not/!
Ternary: condition ? trueValue : falseValue
Grouping: (expression)

String concatenation:

{value + 'suffix'}
{'prefix' + value}
{value1 + ' ' + value2}

Values:

Attribute names: {health} resolves to data-health attribute value
Numbers: {100}, {3.14}
Strings: {'text'}, {"text"}
Booleans: {true}, {false}

Examples:

<!-- Math + string -->
{10 + 5 + 'hp'}  → "15hp"

<!-- Ternary + concat -->
{health > 0 ? health + 'hp' : 'DEAD'}  → "100hp" or "DEAD"

<!-- Complex expression -->
{level > 10 ? 'Veteran Lv' + level : 'Novice'}  → "Veteran Lv15"

<!-- Multiple operations -->
{(damage + bonusDmg) * critMultiplier + ' damage'}  → "150 damage"

Why Expression Templates?

Solves CSS limitations:

✅ Computed values in display text (impossible in CSS content)
✅ String concatenation (impossible in CSS)
✅ Conditional text (no if/else in CSS)
✅ Complex calculations for display

More intuitive than alternatives:

Better than: Compute → attribute → display (two steps)
Syntax: {expr} feels natural
Inline conditionals: Ternary in template, not separate elements

Use Cases

Game development:

<!-- Scaling enemy stats -->
<span data-state-text="{30 + (level - 1) * 10}hp">30hp</span>

<!-- Loot system -->
<span data-state-text="{rarity >= 80 ? 'Legendary' : rarity >= 50 ? 'Rare' : 'Common'}">Common</span>

<!-- Combat log -->
<div data-state-text="{attacker} dealt {damage} damage to {defender}">...</div>

Dynamic UIs:

<!-- User status -->
<span data-state-text="{online ? 'Active now' : 'Last seen ' + lastSeen}">Active now</span>

<!-- Shopping cart -->
<span data-state-text="{itemCount} items ({total} gold)">3 items (150 gold)</span>

<!-- Progress indicators -->
<span data-state-text="{completed}/{total} tasks ({completed/total*100}%)">7/10 tasks (70%)</span>

Form validation:

<span data-state-text="{length < 8 ? 'Too short' : length > 20 ? 'Too long' : 'Valid'}">Valid</span>

Configuration

Expression Templates:

Attribute	Description	Example
`data-state-text="{expr}"`	Template with expressions	`data-state-text="{hp}hp"`
`data-state-text="text {expr} text"`	Mixed static + dynamic	`data-state-text="Level {level} Hero"`

Computed State with Strings:

Attribute	Description	Example
`data-state-compute="name=expr"`	Compute and store result	`data-state-compute="label = hp + 'hp'"`
`data-state-compute="a=expr; b=expr"`	Multiple computations	`data-state-compute="sum = a + b; label = sum + 'hp'"`

Requirements:

data-state-text requires data-state-bind pointing to element with watched attributes
Expressions evaluated using existing State.js expression parser
String concatenation using + operator (auto-detects strings vs numbers)
All watched attributes available as identifiers in expressions

State-Animations.css

State.js includes state-animations.css - a companion stylesheet with predefined animations for common UI patterns and interactive elements.

Include in your project:

<link rel="stylesheet" href="src/state-animations.css">

Available Animation Classes:

UI Feedback & Notifications

.state-notification - Notification slide
.state-warning - Warning shake
.state-success - Success bounce
.state-error - Error shake
.state-loading - Loading spin

Progress & Meter States

.state-health-low - Low value warning pulse
.state-health-critical - Critical state shake
[data-health="0"] - Empty state animation
[data-health="100"] - Full/complete glow

Counter & Score Animations

.state-score-increase - Value increase pop
.state-score-milestone - Milestone celebration
.state-level-up - Level/tier change flash

Status Indicators

.state-powered - Active/powered state glow
.state-invincible - Protected state shimmer
.state-shielded - Shield/protection pulse
.state-stunned - Disabled/paused effect
.state-poisoned - Negative effect pulse
.state-frozen - Frozen/locked shake
.state-burning - Active damage flicker
.state-healing - Positive effect sparkle

View full animation documentation →

Advanced Examples

Multi-Attribute UI Component (Character Stats Demo)

<div id="player"
     data-state
     data-state-watch="health,mana,xp,level"
     data-state-var="true"
     data-health="100"
     data-mana="80"
     data-xp="450"
     data-level="5"
     data-health-max="100"
     data-mana-max="100"
     data-xp-max="1000">

    <div class="health-bar" style="width: var(--state-health-percent)"></div>
    <div class="mana-bar" style="width: var(--state-mana-percent)"></div>
    <div class="xp-bar" style="width: var(--state-xp-percent)"></div>
    <div class="level">Level <span style="--content: var(--state-level)"></span></div>
</div>

Video Progress Indicator

<video data-state
       data-state-media="true"
       data-state-var="true">
    <source src="video.mp4">
</video>

<style>
    video::after {
        content: "";
        width: var(--state-progress);
        height: 5px;
        background: red;
        position: absolute;
        bottom: 0;
        left: 0;
    }
</style>

Boolean Toggle States

<div data-state
     data-state-toggles="active,locked,complete"
     data-active="true"
     data-locked="false"
     data-complete="false">
</div>

/* Automatically applied classes */
.state-active {
    filter: brightness(1.2);
    transform: scale(1.05);
}

.state-locked {
    filter: grayscale(1) brightness(0.6);
    cursor: not-allowed;
}

.state-complete {
    animation: complete-check 0.5s forwards;
}

Clicker Game (Fully declarative)

<div id="clicker"
     data-state
     data-state-watch="score"
     data-state-var="true"
     data-score="0"
     data-score-max="100">

    <h1>Score: <span data-state-display="score">0</span></h1>

    <button data-state
            data-state-trigger
            data-state-bind="clicker"
            data-state-attr="score"
            data-state-increment="1">
        Click Me!
    </button>
</div>

<style>
/* Celebrate milestones with CSS alone */
#clicker[data-score="10"],
#clicker[data-score="20"],
#clicker[data-score="30"] {
    animation: milestone-burst 0.5s ease-out;
}

#clicker[data-score="100"] {
    animation: victory-flash 1s ease-out;
}

/* Progress bar using CSS variables */
#clicker::after {
    content: "";
    width: var(--state-score-percent);
    height: 10px;
    background: linear-gradient(90deg, red, yellow, green);
}
</style>

Volume Control (Increment & Decrement with Auto-Clamping)

<div id="audio"
     data-state
     data-state-watch="volume"
     data-state-var="true"
     data-volume="50"
     data-volume-min="0"
     data-volume-max="100">

    <h2>Volume: <span data-state-display="volume">50</span>%</h2>

    <!-- Decrement button (auto-stops at 0) -->
    <button data-state
            data-state-trigger
            data-state-bind="audio"
            data-state-attr="volume"
            data-state-decrement="10">
        -
    </button>

    <!-- Increment button (auto-stops at 100) -->
    <button data-state
            data-state-trigger
            data-state-bind="audio"
            data-state-attr="volume"
            data-state-increment="10">
        +
    </button>

    <!-- Visual bar updates automatically -->
    <div class="volume-bar" style="width: var(--state-volume-percent);"></div>
</div>

Idle Game with Dynamic Scaling (No JavaScript!)

<div id="idleGame"
     data-state
     data-state-watch="gold,level,clickPower"
     data-state-var="true"
     data-gold="0"
     data-level="1"
     data-clickPower="1">

    <h1>Gold: <span data-state-display="gold">0</span></h1>
    <h2>Level: <span data-state-display="level">1</span></h2>
    <p>Click Power: <span data-state-display="clickPower">1</span></p>

    <!-- Basic click: adds clickPower to gold -->
    <button data-state
            data-state-trigger
            data-state-bind="idleGame"
            data-state-attr="gold"
            data-state-increment="calc(var(--state-clickPower))">
        Mine Gold
    </button>

    <!-- Upgrade: increases clickPower, costs gold -->
    <button data-state
            data-state-trigger
            data-state-bind="idleGame"
            data-state-attr="clickPower"
            data-state-increment="1">
        Upgrade Pick (+1 power)
    </button>

    <!-- Level up: costs increase with level -->
    <button data-state
            data-state-trigger
            data-state-bind="idleGame"
            data-state-attr="level"
            data-state-increment="1">
        Level Up
    </button>
</div>

<style>
/* Different animations per level */
#idleGame[data-level="5"],
#idleGame[data-level="10"] {
    animation: level-milestone 1s ease-out;
}

/* Click power visualization */
#idleGame::after {
    content: "";
    width: calc(var(--state-clickPower) * 10px);
    height: 5px;
    background: gold;
}
</style>

Integration with Other Libraries

State.js is part of a complete CSS/HTML UI development toolkit from iDev Games:

The iDev Games CSS Framework Suite

Five libraries working together for pure CSS/HTML interactive experiences:

Keys.js - Keyboard input tracking
- --key-space, --key-up, --key-down, etc.
Cursor.js - Mouse position tracking
- --cursor-x, --cursor-y, --cursor-speed, etc.
Touch.js - Touch gesture tracking
- --touch-x, --touch-velocity-x, --touch-distance, etc.
Motion.js - Time/animation tracking
- --motion-progress, --motion-time, --motion-loop, etc.
State.js ⭐ - UI state & data binding
- --state-health, --state-score, --state-level, etc.

Combined Example

<div id="game"
     data-state
     data-state-watch="health,score"
     data-health="100"
     data-score="0"

     data-cursor
     data-cursor-var="true"

     data-keys
     data-keys-watch="space,up,down">

    <!-- Health bar follows cursor -->
    <div class="health-bar" style="
        width: var(--state-health-percent);
        transform: translateY(var(--cursor-y));
    "></div>

    <!-- Score pulses when space pressed -->
    <div class="score" style="
        transform: scale(calc(1 + var(--key-space) * 0.5));
    ">
        Score: <span data-state-value="score"></span>
    </div>
</div>

<style>
    /* When health is low AND cursor is idle */
    body.cursor-idle [data-health="10"],
    body.cursor-idle [data-health="20"] {
        animation: warning-pulse 1s infinite;
    }

    /* When up arrow pressed AND health full */
    .key-up[data-health="100"] {
        animation: victory-jump 0.5s ease-out;
    }
</style>

Result: A complete interactive UI system with dynamic data, user input tracking, and reactive animations - all in CSS! Perfect for games, dashboards, data visualizations, and interactive experiences.

Browser Support

State.js uses modern browser APIs:

IntersectionObserver API
MutationObserver API
CSS Custom Properties

Supported browsers:

Chrome/Edge 58+
Firefox 55+
Safari 12.1+
Opera 45+

Performance

State.js is optimized for performance:

✅ Passive event listeners
✅ requestAnimationFrame for DOM updates
✅ Map-based attribute caching
✅ Conditional updates (only when values change)
✅ Efficient MutationObserver usage

Documentation

Examples

Check out the documentation page code as an example: https://github.com/iDev-Games/State-JS/blob/master/index.html

Philosophy

Declarative over Imperative

State.js follows the same philosophy as all iDev Games libraries:

✅ Describe what you want (HTML data attributes)
✅ Style how it looks (CSS)
❌ No complex JavaScript APIs to learn
❌ No framework dependencies

The goal: Enable developers to build reactive, data-driven interfaces using HTML and CSS skills they already have - whether for dashboards, web apps, visualizations, or games.

License

MIT License - see LICENSE file for details

Author

iDev Games

GitHub: @iDev-Games
Dev.to: @idevgames

Contributing

Contributions, issues, and feature requests are welcome!

Feel free to check the issues page.

Show your support

Give a ⭐️ if this project helped you!

推荐订阅源

Echo JS

What is State.js?

Installation

Via NPM

Via CDN

Download Directly

Quick Start

1. Basic Element Visibility Tracking

2. Data Attribute Tracking (Progress Bars & Meters)

3. Form Input Tracking with Auto-Binding

4. Button Triggers (No JavaScript!)

New in v1.1.0: Seven Game Development Extensions

1. data-state-interval — Repeating Timer Triggers

2. data-state-set — Set Exact Value

3. data-state-text — Template String Interpolation

4. data-state-class — Conditional CSS Classes

5. data-state-sound — Procedural Sound Effects

6. data-state-persist — localStorage Save/Restore

7. data-state-event — CustomEvent Dispatch

Complete Game Example (All Declarative)

CSS Variables Created

Visibility & Position

Watched Data Attributes

Form Inputs

Media Elements

Dimensions

Data Attributes API

Activation

Configuration Attributes

Important Notes

Data Attribute Naming (HTML Requirement)

Trigger Chain Atomicity

data-state-value: Numeric and Boolean Duality

Autofire Edge Case

Instantiate: Beyond Game Attributes

Per-State Configuration

New in v1.2.0: HTML Includes

Basic Usage

Creating a Component

How It Works

Use Cases

Configuration

Performance Strategy

Security Considerations

New in v1.3.0: Computed State & Debug API

Computed State

Basic Usage

Multiple Computations

Supported Expressions

Examples

How It Works

Use Cases

Debug API

State.inspectAll()

State.inspect(selector)

State.trace(attrName, enabled)

Usage Examples

Use Cases

New in v1.4.0: Event-Based Triggers

Basic Usage

Supported Events

Debounce (Delay After Rapid Events)

Throttle (Limit Firing Rate)

Visibility Detection

Form Auto-Submit Prevention

Combining with Conditions

Real-World Examples

Live Search Counter

Scroll Progress Tracker

Form Field Tracking

Use Cases

Performance Tips

Configuration

New in v1.5.0: Instance Management

Basic Instantiation

Attribute Overrides

Insert Modes

Instance Counting

Removing Elements