WildflowerJS Logo WildflowerJS

WildflowerJS Reactive JS, No BS*

A no-build reactive JavaScript framework, rooted in the web platform.
No build step. No dependencies. No lock-in.

<script src="wildflower.min.js"></script> ...and start building.

Back to Basics

The code you write is 100% web standard code. HTML stays HTML. JavaScript stays JavaScript. CSS stays CSS. No JSX, no templating language, no custom syntax to learn. If you know the web platform, you already know how to use this.

WildflowerJS extends the web platform. It doesn't replace it.

Your Development Simplified

Because you develop with 100% web standards, every tool in your existing chain already understands the code: IDE, browser DevTools, linter, formatter, screen reader, SEO crawler. Nothing to install, no custom file types, no sourcemaps. Save the file, refresh, and your change is live.

Just be a web developer.

Batteries Included: One Mental Model

Router, SSR, stores, computed properties, two-way binding, event modifiers, data pools, and TypeScript types, all built in, all speaking the same language. Learn data-bind once and you know binding everywhere: lists, pools, stores, forms. There's no five-library stack to keep in sync.

One script tag. Everything you need.

<div data-component="counter">
  <span data-bind="count"></span>
  <button data-action="increment">
    +1
  </button>
</div>

<script>
wildflower.component('counter', {
  state: { count: 0 },
  increment() { this.count++ }
})
</script>

How It Works

data-bind connects state to the DOM.

data-action connects events to methods.

this.count++ triggers a precise DOM update.

Mutate state. The DOM updates.

Two Reactivity Modes

data-list for automatic reactivity: mutate state, DOM updates. data-pool for explicit control: plain objects, zero proxy overhead, you say what changed.

Same template syntax. Different performance profile. From interactive forms to per-frame particle systems. You choose the right tradeoff for the job.

Try it. Right-click, inspect this demo. Every dot is a real DOM element.

See full demo →

Get Started View Demos
* Build Step

Zero Toolchain

Modern frameworks ask you to install a compiler, a bundler, a package manager, hundreds of fragile transitive dependencies, and a framework-specific file format, before you write a single line of your application.

WildflowerJS was built starting from a single principle: no build step, no tooling. Ever.

WildflowerJS asks you to add a script tag.

There's no CLI scaffolding step, no config files, no .vue/.jsx/.svelte source format. You don't debug through sourcemaps or wait on a build pipeline. Your project has zero dependencies.

Performance isn't a tradeoff. Build steps optimize bundle delivery, not the runtime work that follows it. WildflowerJS writes directly to the DOM, with no virtual DOM or reconciliation pass between state change and update, so it doesn't need a build step to be fast.

The framework is full-featured without the toolchain: router, SSR, stores, computed properties, transitions, pools. You don't need a toolchain to use any of it.

my-app/
  index.html
  app.js
  style.css
  wildflower.min.js

That's the entire project. No package.json.
No node_modules. No config files. Ship it.

Zero Install. Zero Attack Surface.

Every dependency you install is trust extended to a maintainer you've never met, running scripts on your dev machine and in your CI. A typical React + Vite + UI‑lib setup pulls in 300+ transitive packages before you write a feature.

Each one is a potential intrusion vector. NPM worms, OAuth chains compromising deploy platforms, postinstall hijacking: the supply chain is now where production code gets compromised, not the deploy. And signing isn't a backstop: Mini Shai‑Hulud (May 2026) compromised 170+ packages whose malicious versions carried valid SLSA Build Level 3 provenance, because the attestation came from build infrastructure the worm had already taken over.

WildflowerJS users don't have this attack surface, by construction. There is no npm install, no postinstall script, no transitive package graph. The framework is one file you copy or pin by hash.

As of v1.1, the same holds for building the framework itself. WildflowerJS bundles with a vendored rollup and terser pipeline pulled as three SHA‑512‑pinned tarballs: no npm install, no transitive packages, no postinstall scripts in the build path. The entire toolchain is three files you verify by hash.

Zero dependencies is the absence of a problem the rest of the industry has not properly addressed.

A typical React/Vue project:

  npm install
  ├── hundreds of packages
  ├── from hundreds of maintainers
  ├── postinstall scripts run on install
  └── tens to hundreds of MB of transitive code

WildflowerJS:

  <script src="wildflower.min.js"></script>
  └── 1 file.
      No transitive dependencies.

Zero Lock-in

WildflowerJS works with the DOM, not instead of it. There's no virtual DOM intercepting your code and no compiler rewriting your markup. The render cycle is yours.

That means Leaflet, DataTables, Chart.js, D3, Three.js, any library that touches the DOM, just works. No wrapper packages or framework-specific escape hatches required. Drop in a script tag and use it.

Because your code is standard HTML and JavaScript, you're never locked in. Your skills transfer and your code is more portable. If you outgrow the framework, your knowledge doesn't expire.

This also means your "ecosystem" is all of the world of vanilla JS. Without compromises or hacks.

<!-- Use any library directly -->
<div data-component="map-view">
  <div id="map" style="height: 400px"></div>
</div>
wildflower.component('map-view', {
  state: { lat: 51.505, lng: -0.09 },
  init() {
    // Leaflet works as-is. No wrappers.
    this._map = L.map('map')
      .setView([this.lat, this.lng], 13);
    L.tileLayer('https://{s}.tile.osm.org'
      + '/{z}/{x}/{y}.png').addTo(this._map);
  }
})

Precise Reactivity

When you write this.count++, WildflowerJS updates the single DOM node bound to count. Nothing else is touched. There's no tree diffing or reconciliation pass to figure that out.

This isn't a tradeoff. You get fine-grained updates and a simple mental model. Change a property, the bound element updates. That's the entire reactivity model.

Other frameworks ask you to learn signals, accessors, memos, effects, and subscription lifecycles to achieve what WildflowerJS does with a property assignment.

wildflower.component('dashboard', {
  state: {
    users: 1420,
    status: 'healthy'
  },
  computed: {
    summary() {
      return this.users + ' users, ' + this.status;
    }
  },
  refresh() {
    this.users = 1421;
    // Only the elements bound to 'users'
    // and 'summary' update. Everything
    // else on the page is untouched.
  }
})

One Reactivity Model. Everywhere.

Components, Stores, and Plugins all share the same reactive foundation. State, computed properties, and methods work identically no matter where they live. Learn it once, it works the same way in a UI component, a global store, or a framework plugin.

Other frameworks make you learn a different system for each layer. React components use hooks, but stores need Redux or Zustand, which are completely different APIs. Vue components use reactive data, but Pinia stores have their own patterns. Every layer is a new mental model.

In WildflowerJS, there's one model. A store is a component without a template. A plugin is an entity that extends the framework itself, adding directives, lifecycle hooks, and services. The same this.count++ triggers the same reactivity everywhere.

This unlocks patterns other frameworks can't express. A store can run headless physics simulations with tick(), feeding data into a component that renders it through a pool, all using the same reactive primitives, no glue code required.

// Component: reactive UI
wildflower.component('cart', {
  state: { items: [] },
  computed: {
    total() { return this.items.length; }
  }
})

// Store: global shared state
wildflower.store('user', {
  state: { name: '', role: 'guest' },
  computed: {
    isAdmin() { return this.role === 'admin'; }
  }
})

// Plugin: extends the framework
wildflower.plugin({
  name: 'notifications',
  state: { items: [], unreadCount: 0 },
  computed: {
    hasUnread() { return this.unreadCount > 0; }
  },
  add(msg) { this.items.push(msg); this.unreadCount++; }
})
// Access globally: wildflower.$notifications.add(...)

// Same state. Same computed. Same methods.

Data Pools

Every framework wraps collection items in reactive proxies, whether the item needs it or not. WildflowerJS gives you a choice: data-list for push reactivity (automatic), data-pool for pull reactivity (explicit control, zero proxy overhead).

Pools render plain objects with the same template syntax as lists. Mutate the object, call markDirty(), and only that item updates. Full CRUD, selection, bulk operations, all faster than the push-reactive path.

And because pools use pull-based rendering, they scale to simulations, games, particle systems, and data visualizations at native frame rate. Use cases that would choke a virtual DOM. No other framework has anything like this.

<div data-component="user-table">
  <tbody data-pool="users" data-key="id">
    <template>
      <tr>
        <td data-bind="name"></td>
        <td data-bind="status"
            data-bind-class="status === 'active'
              ? 'badge success'
              : 'badge inactive'"></td>
      </tr>
    </template>
  </tbody>
</div>
wildflower.component('user-table', {
  pools: { users: {} },

  init() {
    // Populate: plain objects, no proxies
    data.forEach(u => this.pools.users.add(u));
  },

  // Optional: add tick() and the same pool
  // renders every frame. Same template, same
  // data, different rendering frequency.
  // That's the only difference between a
  // display table and a particle system.
})

Built for AI-Assisted Development

Because WildflowerJS is standard HTML and JavaScript, AI code assistants already know how to write it. There's no custom syntax to hallucinate or compiler quirks to work around. The code an AI generates runs exactly as written, with no build step between generation and execution.

We go further. WildflowerJS ships an AI-optimized reference page with patterns, anti-patterns, and examples designed for code generation context windows. Our llms.txt file follows the llms.txt convention for machine-readable documentation.

And for structured app generation, our Universal App Manifest lets you describe an entire application as a JSON schema (components, state, computed properties, methods, templates) and have an AI generate the working code from the manifest, mediated through framework-specific idiom files.

You: "Build me a todo app with
WildflowerJS"

AI reads llms.txt or ai-assistant.html
     ↓
Generates standard HTML + JS
     ↓
<div data-component="todo-app">
  <input data-model="newItem">
  <button data-action="addItem">
    Add
  </button>
  <ul data-list="items">
    <template>
      <li data-bind="text"></li>
    </template>
  </ul>
</div>
     ↓
Open in your browser. It works, and you can read and understand the code.

Attribute Binding

Dynamically set HTML attributes based on component state using data-bind-attr. This is particularly useful for accessibility attributes, data attributes for third-party libraries, and any attribute that needs to change reactively.

Attribute Binding Features:
  • Dynamic HTML attributes via data-bind-attr
  • Object expression syntax for multiple attributes
  • Computed property support
  • Automatic attribute removal for null/undefined/false values
  • Security: Event handlers and framework attributes are blocked

Basic Usage

Single and Multiple Attributes

Use data-bind-attr with an object expression to bind one or more attributes:

<div data-component="attr-demo">
    <!-- Single attribute -->
    <div data-bind-attr="{ 'data-status': status }">
        Status: <span data-bind="status"></span>
    </div>

    <!-- Multiple attributes -->
    <button data-bind-attr="{
        'aria-pressed': isActive,
        'aria-label': buttonLabel,
        'data-action-type': actionType
    }">
        Toggle (<span data-bind="isActive ? 'Active' : 'Inactive'"></span>)
    </button>

    <!-- Controls -->
    <div class="mt-3">
        <button class="btn btn-primary btn-sm me-2" data-action="toggleActive">
            Toggle Active
        </button>
        <button class="btn btn-secondary btn-sm" data-action="cycleStatus">
            Cycle Status
        </button>
    </div>

    <!-- Show current attribute values -->
    <div class="mt-3 p-2" style="background: var(--bs-tertiary-bg); color: var(--bs-body-color); border-radius: 4px; font-family: monospace; font-size: 0.85em;">
        <div>data-status: "<span data-bind="status"></span>"</div>
        <div>aria-pressed: "<span data-bind="isActive"></span>"</div>
        <div>aria-label: "<span data-bind="buttonLabel"></span>"</div>
    </div>
</div>
wildflower.component('attr-demo', {
    state: {
        status: 'pending',
        isActive: false,
        actionType: 'toggle'
    },

    computed: {
        buttonLabel() {
            return this.isActive
                ? 'Click to deactivate'
                : 'Click to activate';
        }
    },

    toggleActive() {
        this.isActive = !this.isActive;
    },

    cycleStatus() {
        const statuses = ['pending', 'in-progress', 'completed'];
        const currentIndex = statuses.indexOf(this.status);
        this.status = statuses[(currentIndex + 1) % statuses.length];
    }
});
Live Preview

Attribute Removal

When a bound value becomes null, undefined, or false, the attribute is automatically removed from the element:

<div data-component="removal-demo">
    <!-- Attribute added/removed based on state -->
    <input type="text" class="form-control"
           placeholder="Type here..."
           data-bind-attr="{
               'disabled': isDisabled,
               'readonly': isReadonly
           }"
           data-bind-class="validationClass">

    <div class="mt-3">
        <label class="form-check form-check-inline">
            <input type="checkbox" class="form-check-input" data-model="isDisabled">
            Disabled
        </label>
        <label class="form-check form-check-inline">
            <input type="checkbox" class="form-check-input" data-model="isReadonly">
            Readonly
        </label>
        <button class="btn btn-sm btn-primary" data-action="cycleValidation">
            Cycle Validation
        </button>
    </div>

    <div class="mt-2 small text-muted">
        disabled: <code data-bind="isDisabled"></code> &middot;
        readonly: <code data-bind="isReadonly"></code> &middot;
        validation: <code data-bind="validationState === null ? 'null (attr removed)' : validationState"></code>
    </div>
</div>
wildflower.component('removal-demo', {
    state: {
        isDisabled: false,
        isReadonly: false,
        validationState: null  // null = no validation styling
    },

    computed: {
        validationClass() {
            // Bootstrap validation classes on the input
            if (this.validationState === 'valid') return 'form-control is-valid';
            if (this.validationState === 'invalid') return 'form-control is-invalid';
            return 'form-control';
        }
    },

    cycleValidation() {
        // null -> valid -> invalid -> null (removed)
        const states = [null, 'valid', 'invalid'];
        const i = states.indexOf(this.validationState);
        this.validationState = states[(i + 1) % states.length];
    }
});
Live Preview

Using in Lists

Data Attributes for Item Identification

A common use case is setting data attributes on list items for integration with JavaScript libraries or for DOM queries:

<div data-component="list-attr-demo">
    <ul class="list-group" data-list="items">
        <template>
            <li class="list-group-item d-flex justify-content-between"
                data-bind-attr="{
                    'data-item-id': id,
                    'data-category': category,
                    'data-priority': priority
                }">
                <span data-bind="name"></span>
                <span class="badge" data-bind-class="priority === 'high' ? 'bg-danger' : priority === 'medium' ? 'bg-warning text-dark' : 'bg-secondary'">
                    <span data-bind="priority"></span>
                </span>
            </li>
        </template>
    </ul>

    <button class="btn btn-sm btn-primary mt-3" data-action="findHighPriority">
        Query High Priority Items
    </button>
    <div class="mt-2 small" data-bind="queryResult"></div>
</div>
wildflower.component('list-attr-demo', {
    state: {
        items: [
            { id: 1, name: 'Task A', category: 'work', priority: 'high' },
            { id: 2, name: 'Task B', category: 'personal', priority: 'low' },
            { id: 3, name: 'Task C', category: 'work', priority: 'medium' },
            { id: 4, name: 'Task D', category: 'urgent', priority: 'high' }
        ],
        queryResult: ''
    },

    findHighPriority() {
        // Query DOM using the data attributes
        const highPriority = this.element.querySelectorAll('[data-priority="high"]');
        const ids = Array.from(highPriority).map(el => el.dataset.itemId);
        this.queryResult = `Found ${ids.length} high priority items: IDs ${ids.join(', ')}`;
    }
});
Live Preview

List Context Variables

Inside lists, you have access to special context variables: _index, _first, and _last:

<div data-component="context-vars-demo">
    <ul class="list-group" data-list="steps">
        <template>
            <li class="list-group-item"
                data-bind-attr="{
                    'data-step-index': _index,
                    'data-is-first': _first,
                    'data-is-last': _last
                }"
                data-bind-class="_first ? 'list-group-item list-group-item-success' : _last ? 'list-group-item list-group-item-info' : 'list-group-item'">
                Step <span data-bind="_index + 1"></span>: <span data-bind="label"></span>
                <span class="badge bg-secondary ms-2" data-show="_first">First</span>
                <span class="badge bg-secondary ms-2" data-show="_last">Last</span>
            </li>
        </template>
    </ul>
</div>
wildflower.component('context-vars-demo', {
    state: {
        steps: [
            { label: 'Initialize' },
            { label: 'Process' },
            { label: 'Validate' },
            { label: 'Complete' }
        ]
    }
});
Live Preview

Third-Party Library Integration

A primary use case for data-bind-attr is integrating with third-party libraries that rely on data attributes to track elements:

SortableJS Integration

Libraries like SortableJS need to identify elements after drag-and-drop operations. Use data-bind-attr to set the identifying attributes:

<!-- Task list with SortableJS integration -->
<ul id="task-list" data-list="tasks">
    <template>
        <li class="task-item"
            data-bind-attr="{ 'data-task-id': id }"
            data-bind-class="done ? 'task-item done' : 'task-item'">
            <span class="drag-handle">⋮⋮</span>
            <span data-bind="text"></span>
        </li>
    </template>
</ul>
// SortableJS reads the data-task-id after drag operations
new Sortable(document.getElementById('task-list'), {
    animation: 150,
    handle: '.drag-handle',
    onEnd(evt) {
        const items = evt.to.querySelectorAll('[data-task-id]');
        const newOrder = Array.from(items).map(el => el.dataset.taskId);

        // Update your state with the new order
        store.reorderTasks(newOrder);
    }
});
Why this works: WildflowerJS has no virtual DOM, so SortableJS can directly manipulate the real DOM elements. The data-bind-attr sets the data-task-id that SortableJS reads to report the new order.

Using Computed Properties

For complex attribute logic, use a computed property that returns an attributes object:

<div data-component="computed-attr-demo">
    <!-- Using computed property for complex attribute logic -->
    <div data-bind-attr="cardAttributes"
         style="padding: 1rem; border: 2px solid; border-radius: 8px;">
        <h5 data-bind="title"></h5>
        <p data-bind="description"></p>
    </div>

    <div class="mt-3">
        <select class="form-select form-select-sm d-inline-block w-auto me-2" data-model="status">
            <option value="draft">Draft</option>
            <option value="published">Published</option>
            <option value="archived">Archived</option>
        </select>
        <label class="form-check form-check-inline">
            <input type="checkbox" class="form-check-input" data-model="featured">
            Featured
        </label>
    </div>

    <div class="mt-2 small" style="font-family: monospace;">
        Computed attributes: <span data-bind="attributeDisplay"></span>
    </div>
</div>
wildflower.component('computed-attr-demo', {
    state: {
        title: 'Article Title',
        description: 'This card uses computed attributes.',
        status: 'draft',
        featured: false
    },

    computed: {
        cardAttributes() {
            const attrs = {
                'data-status': this.status,
                'aria-label': `${this.title} - ${this.status}`
            };

            // Set featured attribute - use null to remove when unchecked
            attrs['data-featured'] = this.featured ? 'true' : null;

            // Add role for accessibility
            attrs['role'] = 'article';

            return attrs;
        },

        attributeDisplay() {
            const attrs = this.cardAttributes;
            return Object.entries(attrs)
                .map(([k, v]) => `${k}="${v}"`)
                .join(', ');
        }
    }
});
Live Preview

Accessibility (ARIA) Attributes

data-bind-attr fully supports ARIA attributes, making it straightforward to build accessible components with dynamic state. Hyphenated names like aria-expanded are automatically handled. Just quote them in the object expression.

Common ARIA Patterns

<div data-component="accessible-panel">
    <!-- Toggle button with aria-expanded -->
    <button data-action="toggle"
            data-bind-attr="{
                'aria-expanded': isOpen,
                'aria-controls': 'panel-content'
            }">
        <span data-bind="isOpen ? 'Collapse' : 'Expand'"></span> Details
    </button>

    <!-- Collapsible panel -->
    <div id="panel-content" role="region"
         data-show="isOpen"
         data-bind-attr="{ 'aria-hidden': !isOpen }">
        Panel content here
    </div>

    <!-- Status with aria-live for screen readers -->
    <div aria-live="polite" data-bind-attr="{
        'aria-busy': isLoading
    }">
        <span data-bind="statusMessage"></span>
    </div>
</div>
wildflower.component('accessible-panel', {
    state: {
        isOpen: false,
        isLoading: false,
        statusMessage: 'Ready'
    },

    toggle() {
        this.isOpen = !this.isOpen;
    }
});

ARIA in Lists

ARIA attributes work inside data-list templates just like any other attribute binding:

<ul role="listbox" data-list="options">
    <template>
        <li role="option"
            data-bind-attr="{
                'aria-selected': selected,
                'aria-disabled': disabled
            }"
            data-action="selectOption">
            <span data-bind="label"></span>
        </li>
    </template>
</ul>
Tip: Use data-bind-attr for dynamic ARIA attributes that change with state (like aria-expanded or aria-selected). For static ARIA attributes that never change (like role="button"), just write them directly in your HTML. No binding needed.

Security

data-bind-attr includes security measures to prevent common attack vectors:

Blocked Attributes

Category Blocked Attributes Reason
Event Handlers onclick, onload, onerror, etc. Prevents XSS via inline event handlers
Framework Directives data-bind, data-action, data-list, etc. Prevents framework state corruption
Style/Class class, style Use dedicated bindings instead

URL Sanitization

For URL-type attributes (href, src, formaction), dangerous protocols are blocked:

  • javascript: URLs are blocked
  • data:text/html in src attributes is blocked (iframe XSS vector)

Syntax Reference

Syntax Example Description
Object expression data-bind-attr="{ 'data-id': id }" Bind attributes from an inline object
Multiple attributes data-bind-attr="{ 'aria-label': label, 'data-status': status }" Bind multiple attributes at once
Computed property data-bind-attr="myAttrs" Use a computed property that returns an object (computed: prefix optional)
Expressions in values data-bind-attr="{ 'aria-expanded': isOpen ? 'true' : 'false' }" Use ternary or other expressions for values
Note: data-bind-attr also supports the data-wf- prefix (e.g., data-wf-bind-attr) for compatibility with third-party libraries that might conflict with the standard prefix.

Best Practices

Recommendations:
  • Use computed properties for complex attribute logic - keeps templates clean
  • Quote hyphenated attribute names - { 'data-item-id': id } not { data-item-id: id }
  • Use semantic attributes - prefer aria-* for accessibility over custom data-*
  • Don't overuse - for class use data-bind-class, for style use data-bind-style
  • Return null/undefined/false to remove an attribute rather than setting it to empty string
Previous Style Binding
Next Event Handling