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.

TypeScript Support DEV

Complete TypeScript definitions for full IDE support, type checking, and runtime binding validation.

Sandbox Examples: TypeScript examples run in isolated iframes demonstrating type-safe patterns and runtime validation features.

Overview

WildflowerJS provides comprehensive TypeScript support through:

  • Complete type definitions - Full .d.ts file with 1200+ lines covering all APIs
  • Generic components - Type-safe state management with ComponentDefinition<TState>
  • Runtime validation - Catch binding errors during development with types property
  • JSDoc annotations - Rich documentation in source for JavaScript users
  • IDE integration - IntelliSense, autocomplete, and inline documentation

Installation

The TypeScript definitions are included in the WildflowerJS package. For TypeScript projects:

// tsconfig.json
{
  "compilerOptions": {
    "target": "ES2020",
    "lib": ["ES2020", "DOM", "DOM.Iterable"],
    "strict": true,
    "esModuleInterop": true
  },
  "include": ["src/**/*.ts", "wildflowerJS.d.ts"]
}

For JavaScript projects, you can still benefit from type definitions through JSDoc comments and IDE support:

// Enable TypeScript checking in JS files via JSDoc
// @ts-check

/** @type {import('./wildflowerJS').WildflowerOptions} */
const options = {
    debug: true,
    autoInit: false
};

const wf = new WildflowerJS('#app', options);

Type Definitions

WildflowerJS exports the following key types:

Core Types

Type Description
WildflowerJSMain framework class
WildflowerOptionsFramework initialization options
ComponentDefinition<T>Component definition with typed state
ComponentInstanceRuntime component instance
ComponentStateBase state type

Router Types

Type Description
RouteManagerRouter class
RouteManagerOptionsRouter configuration
RouteConfigRoute definition
RouteCurrent route state
RouteGuardNavigation guard function

Store Types

Type Description
StoreConfig<T>Store definition with typed state
StoreContext<T>Store instance with typed methods

Typed Components

Define components with strongly-typed state for full IDE support:

// Define a typed interface for your component state
interface CounterState {
    count: number;
    step: number;
    label: string;
}

// Use ComponentDefinition<T> for type-safe components
const counterDef: ComponentDefinition<CounterState> = {
    state: {
        count: 0,
        step: 1,
        label: 'Counter'
    },

    computed: {
        doubled() {
            // ContextProxy auto-resolves state properties
            // IDE autocomplete shows: count, step, label
            return this.count * 2;
        }
    },

    increment() {
        this.count += this.step;
    },

    setStep(value: number) {
        // TypeScript ensures value is a number
        this.step = value;
    }
};

wildflower.component('typed-counter', counterDef);

With this definition, TypeScript provides:

  • Autocomplete - Type this. and see all state and computed properties
  • Error detection - this.invalid shows a red squiggle
  • Type checking - this.count = "string" is caught at compile time
  • Refactoring - Rename a property and all references update

Typed Stores

Create strongly-typed stores with full IDE support:

interface CartState {
    items: Array<{ id: number; name: string; price: number; quantity: number }>;
    total: number;
}

const storeConfig: StoreConfig<CartState> = {
    state: {
        items: [],
        total: 0
    },
    computed: {
        itemCount() {
            return this.items.reduce((sum, item) => sum + item.quantity, 0);
        }
    },
    watch: {
        items(newItems, oldItems) {
            this.total = newItems.reduce(
                (sum, item) => sum + item.price * item.quantity,
                0
            );
        }
    },
    addItem(item: { id: number; name: string; price: number }) {
        this.items.push({ ...item, quantity: 1 });
    },
    removeItem(id: number) {
        this.items = this.items.filter(i => i.id !== id);
    }
};

const cartStore: StoreContext<CartState> = wf.store('cart', storeConfig);

Runtime Binding Validation

WildflowerJS provides runtime type checking for development builds through the types property:

TypeScript Example Runtime Type Validation Open Full Example
Runtime Type Definition:
wildflower.component('validated-form', {
    state: {
        username: '',
        age: 0,
        isActive: false,
        tags: [],
        metadata: {}
    },
    // Runtime type validation (development mode)
    types: {
        username: 'string',
        age: 'number',
        isActive: 'boolean',
        tags: 'array',
        metadata: 'object'
    },
    updateAge(event, element) {
        // Framework validates: is the new value a number?
        this.age = parseInt(element.value, 10);
    }
});
Development Feature: Type mismatches are logged as warnings in development mode. This helps catch errors like binding a string to a number field or assigning an array where an object is expected.

Supported Runtime Types

Type String JavaScript Type Example Values
'string'string'', 'hello'
'number'number0, 42, 3.14
'boolean'booleantrue, false
'array'Array[], [1, 2, 3]
'object'object{}, { key: 'value' }
'function'function() => {}
'any'anyNo validation

IDE Features

With TypeScript definitions, your IDE provides:

IntelliSense & Autocomplete

  • Property suggestions - See all state properties when typing this.
  • Method signatures - View parameter types and return values
  • Quick documentation - Hover over methods to see JSDoc comments
  • Error detection - Red squiggles for type mismatches

Supported IDEs

  • VS Code - Full TypeScript support out of the box
  • WebStorm - Excellent TypeScript integration
  • Vim/Neovim - With TypeScript language server
  • Any IDE with TypeScript support

Example: IDE Autocomplete

// After typing "wf.", IDE suggests:
// - component()
// - store()
// - getStore()
// - router()
// - plugin()
// - on()
// - ... all public methods

// After typing "this." in a component:
// - All state properties (auto-resolved)
// - Computed properties (auto-resolved)

// After typing "router.", IDE suggests:
// - navigate()
// - onRoute()
// - beforeEach()
// - getCurrentRoute()
// - ... all router methods

Best Practices

Define Interfaces for Complex State

// Define interface for clarity and reuse
interface UserState {
    profile: {
        name: string;
        email: string;
        avatar: string;
    };
    preferences: {
        theme: 'light' | 'dark';
        notifications: boolean;
    };
    isLoading: boolean;
}

// Use the interface in component definition
const userComponent: ComponentDefinition<UserState> = {
    state: {
        profile: { name: '', email: '', avatar: '' },
        preferences: { theme: 'light', notifications: true },
        isLoading: false
    }
};

Use Runtime Types for JavaScript Projects

// Even without TypeScript, get runtime validation
wildflower.component('user-form', {
    state: {
        name: '',
        age: 0,
        email: ''
    },
    types: {
        name: 'string',
        age: 'number',
        email: 'string'
    }
});

Combine TypeScript and Runtime Validation

// TypeScript catches compile-time errors
// Runtime types catch data-flow errors (e.g., API responses)
interface FormState {
    count: number;
    name: string;
}

const formDef: ComponentDefinition<FormState> = {
    state: { count: 0, name: '' },
    types: { count: 'number', name: 'string' }, // Runtime check

    async loadFromAPI() {
        const data = await fetch('/api/data').then(r => r.json());
        // TypeScript ensures data shape at compile time
        // Runtime types warn if API returns wrong types
        this.count = data.count;
        this.name = data.name;
    }
};

Type Guards for Complex Logic

interface Item {
    id: number;
    type: 'product' | 'service';
    price: number;
}

function isProduct(item: Item): item is Item & { type: 'product' } {
    return item.type === 'product';
}

// In component methods:
processItem(item: Item) {
    if (isProduct(item)) {
        // TypeScript knows item.type is 'product' here
        this.calculateProductTax(item);
    }
}
Tip: Enable strict: true in your tsconfig.json for the best type checking experience. This catches more potential issues at compile time.