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.

Navigation UX SPA+

View transitions, hash fragment navigation, scroll restoration, and history state management.

View Transitions

The View Transitions API provides smooth, animated transitions between pages. WildflowerJS integrates with the browser's native View Transitions API for seamless navigation animations.

Browser Support: View Transitions are supported in Chrome 111+, Edge 111+, Firefox 129+, and Safari 18+. The router gracefully falls back to instant updates in unsupported browsers.

Enabling View Transitions

// Enable via createRouter factory
const router = wildflower.createRouter({
    mode: 'hash',
    viewTransitions: true,  // Enable view transitions
    routes: [
        { path: '/', handler: () => showHome() },
        { path: '/about', handler: () => showAbout() }
    ]
});

// Or enable after creation
const router = wildflower.createRouter({ mode: 'hash' });
router.setViewTransitions(true);

Checking API Availability

// Check if browser supports View Transitions
if (router.viewTransitionsAvailable) {
    console.log('View Transitions API is supported!');
}

// Check if transitions are both enabled AND supported
if (router.viewTransitionsEnabled) {
    console.log('View transitions will be used for navigation');
}

Transition Events

Subscribe to transition lifecycle events:

// When a view transition starts
router.on('viewTransitionStart', ({ from, to, transition }) => {
    console.log(`Transitioning from ${from} to ${to}`);
    // 'transition' is the native ViewTransition object
});

// When a view transition completes
router.on('viewTransitionEnd', ({ from, to }) => {
    console.log('Transition complete!');
});

// If a transition fails
router.on('viewTransitionError', ({ error, from, to }) => {
    console.error('Transition failed:', error);
});

Skipping Transitions

Skip the animation for specific navigations:

// Skip transition for this navigation
router.navigate('/login', { skipTransition: true });

// Useful for:
// - Programmatic redirects (e.g., after form submission)
// - Navigation from guards
// - Initial page load

Per-Route Transition Config

Configure transitions per route:

const router = wildflower.createRouter({
    viewTransitions: true,
    routes: [
        {
            path: '/',
            handler: showHome,
            transition: 'fade'  // Custom transition type (for CSS targeting)
        },
        {
            path: '/modal',
            handler: showModal,
            transition: false   // Disable transitions for this route
        }
    ]
});

CSS Customization

Style your transitions with CSS:

/* Name your content for targeting */
.page-content {
    view-transition-name: page-content;
}

/* Customize the transition animations */
::view-transition-old(page-content) {
    animation: 200ms ease-out both slide-to-left;
}

::view-transition-new(page-content) {
    animation: 200ms ease-out both slide-from-right;
}

/* Define the animations */
@keyframes slide-to-left {
    from { transform: translateX(0); opacity: 1; }
    to { transform: translateX(-30px); opacity: 0; }
}

@keyframes slide-from-right {
    from { transform: translateX(30px); opacity: 0; }
    to { transform: translateX(0); opacity: 1; }
}
Router Example View Transitions Demo Open Full Example
Try it: Toggle view transitions on/off and navigate between pages. Watch the smooth slide animation when transitions are enabled.

Runtime Control

// Enable/disable at runtime
router.setViewTransitions(true);
router.setViewTransitions(false);

// Access current transition during animation
router.on('viewTransitionStart', () => {
    const transition = router.currentTransition;
    // Wait for animation to be ready
    transition.ready.then(() => {
        console.log('Animation started');
    });
    // Wait for animation to finish
    transition.finished.then(() => {
        console.log('Animation finished');
    });
});

Hash Fragment Navigation

Navigate to specific sections within a page using hash fragments. The router parses fragments from the URL and can automatically scroll to the matching element.

Basic Usage

// Navigate with a hash fragment
router.navigate('/docs/api#methods');

// Or pass hash as an option
router.navigate('/docs/api', { hash: '#methods' });

// Access hash in route handlers
router.onRoute('/docs/:section', {
    handler: ({ params, hash }) => {
        showDocs(params.section);
        // hash === '#methods' for /docs/api#methods
    }
});
Hash Mode Conflict: In hash mode, the URL's # is already used for routing (e.g. page.html#/docs/api), so hash fragments cannot appear in href attributes like href="#/docs/api#methods"; the browser treats everything after the first # as a single fragment. Use programmatic navigation instead: router.navigate('/docs/api', { hash: '#methods' }). In history mode this limitation does not apply.

Auto-Scroll Behavior

When a hash fragment is present, the router automatically scrolls to the element with a matching id. It retries up to 10 times (100ms apart) to handle dynamically rendered content.

<!-- The router will scroll to this element for #features -->
<section id="features">
    <h2>Features</h2>
    <p>Content here...</p>
</section>

Hash in Named Routes

// Generate URL with hash
const url = router.getRouteUrl('docs', { section: 'api' });
// Returns: /docs/api, append hash manually:
router.navigate(url + '#methods');
Router Example Hash Fragment Navigation Open Full Example
Try it: Click the section links to navigate with hash fragments. The content scrolls to the target section and the route info updates.

Scroll Position Restoration

The router automatically saves scroll position before navigation. On browser back/forward, the saved position is restored.

Default Behavior

  • New navigation scrolls to the top (or to a hash fragment if present)
  • Back/forward restores the previous scroll position

Custom Scroll Behavior

const router = wildflower.createRouter({
    scrollBehavior(to, from, savedPosition) {
        // savedPosition is available on back/forward navigation
        if (savedPosition) {
            return savedPosition;  // { x: number, y: number }
        }

        // Scroll to hash fragment
        if (to.hash) {
            return { selector: to.hash };
        }

        // Default: scroll to top
        return { x: 0, y: 0 };
    }
});

Scroll Return Values

Return Value Effect
{ x, y }Scroll to coordinates
{ selector: '#id' }Scroll to element (smooth)
{ el: '#id' }Alias for selector
null / undefinedNo scroll change

History State

Attach custom state to navigation entries. State is stored in history.state and survives back/forward navigation.

// Navigate with custom state
router.navigate('/products/42', {
    state: { fromList: true, scrollIndex: 15 }
});

// Access state in popstate (back/forward)
window.addEventListener('popstate', (e) => {
    if (e.state && e.state.fromList) {
        // User came back from product detail to list
        restoreListPosition(e.state.scrollIndex);
    }
});
Merged with Scroll: Custom state is merged with the router's automatic scroll position data. Your properties are preserved alongside scrollX, scrollY, and path.