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 →

* 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.

Advanced Plugin Patterns CORE+

Advanced plugin techniques including service providers, reactive state binding, watchers, subscriptions, and complete real-world examples.

Watching State Changes

Use the watch object to react to state changes declaratively:

wildflower.plugin({
    name: 'cart',
    state: {
        items: [],
        total: 0
    },

    watch: {
        // Watch a specific property
        total(newValue, oldValue) {
            console.log(`Total changed: ${oldValue} -> ${newValue}`)
        },

        // Watch array changes
        items(newItems, oldItems) {
            console.log(`Cart now has ${newItems.length} items`)
        }
    },

    addItem(item) {
        this.items = [...this.items, item]
        this.total += item.price
    },

    install(wf) {}
})

Programmatic Subscriptions

Use subscribe() for dynamic state observation with automatic cleanup:

// Subscribe to a specific path
const unsubscribe = wildflower.$cart.subscribe('total', (newValue, oldValue) => {
    updateCheckoutButton(newValue)
})

// Later, clean up the subscription
unsubscribe()

Binding Plugin State to the DOM

Use $entity.path in data-bind to automatically update the UI when plugin state changes:

<!-- Display plugin state -->
<span data-bind="$cart.total"></span>

<!-- Display computed property -->
<span data-bind="$cart.itemCount"></span>

<!-- Nested properties work too -->
<span data-bind="$user.profile.name"></span>

When plugin state changes, bound elements update automatically - no manual refresh needed.

Service Providers

Providing Services

Register services that components can use:

// Provide an HTTP service
wildflower.provide('http', {
    async get(url) {
        const response = await fetch(url)
        return response.json()
    },
    async post(url, data) {
        const response = await fetch(url, {
            method: 'POST',
            headers: { 'Content-Type': 'application/json' },
            body: JSON.stringify(data)
        })
        return response.json()
    }
})

// Provide configuration
wildflower.provide('config', {
    apiUrl: 'https://api.example.com',
    debug: true
})

// Provide class instances
class Logger {
    logs = []
    log(msg) { this.logs.push(msg) }
}
wildflower.provide('logger', new Logger())

// Provide utility functions
wildflower.provide('formatDate', (date) => {
    return new Date(date).toLocaleDateString()
})

Using Services in Components

Declare services with the uses property:

wildflower.component('user-list', {
    uses: ['http', 'config'],  // Services this component uses

    state: { users: [] },

    async init() {
        // Services available as $serviceName
        const url = this.$config.apiUrl + '/users'
        this.users = await this.$http.get(url)
    }
})

Using Services in Plugins

Plugins can also declare services they use:

// First, provide services
wildflower.provide('http', httpService)
wildflower.provide('auth', authService)

// Then create a plugin that uses them
wildflower.plugin({
    name: 'dataSync',
    version: '1.0.0',
    uses: ['http', 'auth'],  // Services this plugin uses

    install(wf) {
        // Services available as this.$http, this.$auth
        if (this.$auth.isLoggedIn()) {
            this.$http.get('/sync')
        }
    }
})

Shared Services

The same service instance is shared across all components:

// The same logger instance is shared everywhere
wildflower.provide('logger', new Logger())

wildflower.component('comp-a', {
    uses: ['logger'],
    init() { this.$logger.log('Component A') }
})

wildflower.component('comp-b', {
    uses: ['logger'],
    init() { this.$logger.log('Component B') }
})

// Both components share the same Logger instance

Complete Plugin Example: Analytics

A complete analytics plugin demonstrating multiple features:

wildflower.plugin({
    name: 'analytics',
    version: '1.0.0',

    state: {
        events: [],
        sessionStart: Date.now()
    },

    track(event, data = {}) {
        this.events.push({
            event,
            data,
            timestamp: Date.now()
        })
    },

    getSessionDuration() {
        return Date.now() - this.sessionStart
    },

    computed: {
        eventCount() {
            return this.events.length
        }
    },

    install(wf) {
        // Add tracking directive
        wf.directive('track-click', {
            init(element, value, context) {
                element.addEventListener('click', () => {
                    wildflower.$analytics.track('click', {
                        element: value,
                        component: context.component?.name
                    })
                })
            }
        })

        // Provide a track service for components
        wf.provide('track', (event, data) => {
            wildflower.$analytics.track(event, data)
        })

        // Hook into component lifecycle
        wf.hook('component:afterInit', (instance) => {
            wildflower.$analytics.track('component:init', {
                name: instance.name
            })
        })
    }
})

Using the Analytics Plugin

<!-- Use the tracking directive -->
<button data-track-click="purchase-button">Buy Now</button>

<!-- Use in component -->
<div data-component="checkout">
    <button data-action="complete">Complete Order</button>
</div>
wildflower.component('checkout', {
    uses: ['track'],  // Declare the service
    state: { total: 0 },

    complete() {
        // Use the track service
        this.$track('checkout:complete', { total: this.total })

        // Or access plugin directly
        console.log('Events tracked:', wildflower.$analytics.eventCount)
    }
})

Complete Plugin Example: Shopping Cart

This example demonstrates all reactive plugin features working together:

wildflower.plugin({
    name: 'cart',
    version: '1.0.0',

    state: {
        items: [],
        discount: 0
    },

    computed: {
        itemCount() {
            return this.items.length
        },
        subtotal() {
            return this.items.reduce((sum, item) => sum + item.price, 0)
        },
        total() {
            return this.subtotal - this.discount
        }
    },

    watch: {
        items(newItems) {
            // Persist to localStorage whenever items change
            localStorage.setItem('cart', JSON.stringify(newItems))
        }
    },

    add(product) {
        this.items = [...this.items, product]
    },

    remove(index) {
        this.items = this.items.filter((_, i) => i !== index)
    },

    applyDiscount(amount) {
        this.discount = amount
    },

    clear() {
        this.reset()  // Reset to initial state
    },

    install(wf) {
        // Load saved cart on startup
        const saved = localStorage.getItem('cart')
        if (saved) {
            this.items = JSON.parse(saved)
        }
    }
})

HTML with Automatic Updates

<div data-component="cart-widget">
    <!-- These update automatically when cart changes -->
    <span data-bind="$cart.itemCount"></span> items
    <strong>$<span data-bind="$cart.total"></span></strong>
    <button data-action="clearCart">Clear</button>
</div>

<div data-component="product-card">
    <h3 data-bind="name"></h3>
    <p>$<span data-bind="price"></span></p>
    <button data-action="addToCart">Add to Cart</button>
</div>
wildflower.component('cart-widget', {
    state: {},
    clearCart() {
        wildflower.$cart.clear()
    }
})

wildflower.component('product-card', {
    state: { name: 'Widget', price: 29.99 },
    addToCart() {
        wildflower.$cart.add({
            name: this.name,
            price: this.price
        })
    }
})

Click "Add to Cart" and the cart widget updates instantly - no events, no callbacks, just reactive state.

Complete Directive Example: Tooltips Plugin

This interactive example demonstrates a production-ready tooltip plugin using all three directive lifecycle hooks. Hover over buttons and list items to see tooltips in action.

<div data-component="tooltip-demo">
    <!-- Static tooltip -->
    <div class="mb-3">
        <h6>Static Tooltip</h6>
        <button class="btn btn-primary" data-tooltip="This is a static tooltip message">
            Hover Me (Static)
        </button>
    </div>

    <!-- Dynamic tooltip bound to state -->
    <div class="mb-3">
        <h6>Dynamic Tooltip (Bound to State)</h6>
        <button class="btn btn-success" data-tooltip="dynamicMessage">
            Hover Me (Dynamic)
        </button>
        <div class="mt-2">
            <input type="text" class="form-control" data-model="dynamicMessage"
                   placeholder="Type to change tooltip...">
        </div>
    </div>

    <!-- Tooltips in list items -->
    <div class="mb-3">
        <h6>Tooltips in List Items</h6>
        <ul class="list-group" data-list="items">
            <template>
                <li class="list-group-item" data-tooltip="description">
                    <strong data-bind="name"></strong>
                </li>
            </template>
        </ul>
        <button class="btn btn-outline-primary btn-sm mt-2" data-action="addItem">
            Add Item
        </button>
    </div>

    <!-- Conditional tooltip (data-show) -->
    <div class="mb-3">
        <h6>Conditional Visibility</h6>
        <button class="btn btn-outline-secondary btn-sm" data-action="toggleSection">
            Toggle Section
        </button>
        <span class="ms-2 text-muted" data-bind="showSection ? 'Visible' : 'Hidden'"></span>
        <div data-show="showSection" class="mt-2 p-2 bg-light rounded">
            <button class="btn btn-warning" data-tooltip="This tooltip hides when section hides">
                Conditional Tooltip
            </button>
        </div>
    </div>
</div>
// Register the tooltip plugin with directive
wildflower.plugin({
    name: 'tooltips',
    install(wf) {
        wf.directive('tooltip', {
            // Called when element with data-tooltip is discovered
            init(element, value, context) {
                const text = context.resolvedValue || value;

                // Create tooltip element
                const tooltip = document.createElement('div');
                tooltip.className = 'wf-tooltip';
                tooltip.textContent = text;
                document.body.appendChild(tooltip);

                // Store references for cleanup
                element._wfTooltip = tooltip;
                element._wfTooltipText = text;

                element._wfTooltipShow = () => {
                    tooltip.textContent = element._wfTooltipText;
                    const rect = element.getBoundingClientRect();
                    tooltip.style.left = rect.left + (rect.width / 2) - (tooltip.offsetWidth / 2) + 'px';
                    tooltip.style.top = rect.top - tooltip.offsetHeight - 10 + 'px';
                    tooltip.classList.add('visible');
                };

                element._wfTooltipHide = () => {
                    tooltip.classList.remove('visible');
                };

                element.addEventListener('mouseenter', element._wfTooltipShow);
                element.addEventListener('mouseleave', element._wfTooltipHide);
            },

            // Called when bound value changes
            update(element, newValue, oldValue, context) {
                if (element._wfTooltip) {
                    element._wfTooltipText = newValue;
                    if (element._wfTooltip.classList.contains('visible')) {
                        element._wfTooltip.textContent = newValue;
                    }
                }
            },

            // Called when element is removed from DOM
            destroy(element, context) {
                if (element._wfTooltip) element._wfTooltip.remove();
                if (element._wfTooltipShow) {
                    element.removeEventListener('mouseenter', element._wfTooltipShow);
                }
                if (element._wfTooltipHide) {
                    element.removeEventListener('mouseleave', element._wfTooltipHide);
                }
                delete element._wfTooltip;
                delete element._wfTooltipShow;
                delete element._wfTooltipHide;
                delete element._wfTooltipText;
            }
        });
    }
});

// Demo component using the tooltip directive
wildflower.component('tooltip-demo', {
    state: {
        dynamicMessage: 'This tooltip updates as you type!',
        showSection: true,
        items: [
            { name: 'Apple', description: 'A crisp, sweet fruit' },
            { name: 'Banana', description: 'A yellow tropical fruit' },
            { name: 'Cherry', description: 'A small red stone fruit' }
        ],
        itemCounter: 3
    },

    toggleSection() {
        this.showSection = !this.showSection;
    },

    addItem() {
        this.itemCounter++;
        this.items.push({
            name: 'Item ' + this.itemCounter,
            description: 'Description for item ' + this.itemCounter
        });
    }
});
.wf-tooltip {
    position: fixed;
    background: #333;
    color: white;
    padding: 8px 12px;
    border-radius: 4px;
    font-size: 13px;
    z-index: 10000;
    pointer-events: none;
    opacity: 0;
    transition: opacity 0.15s;
    max-width: 250px;
    box-shadow: 0 2px 8px rgba(0,0,0,0.2);
}

.wf-tooltip.visible {
    opacity: 1;
}

/* Arrow pointing down */
.wf-tooltip::after {
    content: '';
    position: absolute;
    top: 100%;
    left: 50%;
    transform: translateX(-50%);
    border: 6px solid transparent;
    border-top-color: #333;
}
Live Preview
Key Points:
  • init() creates the tooltip DOM element and attaches event listeners
  • update() handles reactive state changes (typing in input updates tooltip)
  • destroy() cleans up DOM elements and event listeners when element is removed
  • The directive works with static values, state bindings, list items, and conditional rendering
  • Always store references on the element for proper cleanup in destroy()

Plugin API Reference

Method Description
wildflower.plugin(plugin, options) Register a plugin (function or object with install method)
wildflower.directive(name, handlers) Register a custom directive
wildflower.hook(event, callback) Register a lifecycle hook callback
wildflower.provide(key, value) Register a service that components can use
wildflower.getService(key) Retrieve a provided service
wildflower.hasProvider(key) Check if a service is registered
wildflower.hasPlugin(name) Check if a plugin is registered
wildflower.getPlugin(name) Get plugin info by name
wildflower.listPlugins() List all registered plugins
wildflower.$pluginName Access plugin state, methods, and computed properties
wildflower.$pluginName.state The plugin's reactive state object
wildflower.$pluginName.reset() Reset plugin state to initial values
wildflower.$pluginName.subscribe(path, callback) Subscribe to state changes, returns unsubscribe function

Best Practices

  • Name your plugins: Always provide a name and version for easier debugging
  • Clean up: Implement destroy handlers for directives to prevent memory leaks
  • Keep plugins focused: Each plugin should do one thing well
  • Document services: Clearly state which services your plugin provides or requires
  • Handle missing providers: Check if services exist before using
  • Explicit is better: Declare services in uses to make component requirements clear