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.

Router API

Client-side routing for single-page applications.

SPA Package Required: The router is included in the SPA, Full, and AI packages. It's not available in the Lite or Core packages.

wildflower.createRouter()

Create and configure the application router.

Signature

wildflower.createRouter(config: RouterConfig): Router

Config Options

OptionTypeDefaultDescription
mode 'hash' | 'history' 'hash' URL handling mode
routes RouteConfig[] [] Route definitions
defaultRoute string '/' Fallback route path
scrollBehavior function - Custom scroll handling
viewTransitions boolean false Enable View Transitions API for animated page changes

Example

const router = wildflower.createRouter({
    mode: 'history',
    routes: [
        { path: '/', component: 'home-page' },
        { path: '/about', component: 'about-page' },
        { path: '/users/:id', component: 'user-profile' },
        { path: '/products', component: 'product-list' },
        { path: '*', component: 'not-found' }
    ]
});
// Router is automatically initialized: no separate init() call needed

Route Configuration

Each route is an object with these properties:

RouteConfig

PropertyTypeDescription
path string URL path pattern
component string Component name to render
name string Named route for programmatic navigation
meta object Custom route metadata
beforeEnter function Route-specific guard, runs before entering this route
beforeLeave function Route-specific guard, runs before leaving this route
children RouteConfig[] Nested route definitions

Path Patterns

const routes = [
    // Static path
    { path: '/about', component: 'about-page' },

    // Dynamic parameter
    { path: '/users/:id', component: 'user-profile' },

    // Multiple parameters
    { path: '/posts/:category/:slug', component: 'blog-post' },

    // Optional parameter
    { path: '/search/:query?', component: 'search-results' },

    // Wildcard (catch-all)
    { path: '*', component: 'not-found' }
];

History Modes

Hash Mode (Default)

Uses URL hash for navigation. Works without server configuration.

// URLs like: example.com/#/users/123
wildflower.createRouter({
    mode: 'hash',
    routes: [...]
});

History Mode

Uses real URLs via History API. Requires server-side fallback configuration.

// URLs like: example.com/users/123
wildflower.createRouter({
    mode: 'history',
    routes: [...]
});
Server Configuration Required: History mode requires your server to return the main HTML file for all routes. Without this, direct URL access or page refresh will result in 404 errors.

Route Parameters

Access dynamic route parameters in your components.

Accessing Parameters

// Route: /users/:id
wildflower.component('user-profile', {
    state: {
        user: null,
        loading: true
    },

    async init() {
        // Access route params via the router
        const params = window.router.currentRoute.params;
        const userId = params.id;

        // Fetch user data
        const response = await fetch(`/api/users/${userId}`);
        this.user = await response.json();
        this.loading = false;
    }
});

Multiple Parameters

// Route: /posts/:category/:slug
wildflower.component('blog-post', {
    init() {
        const { category, slug } = window.router.currentRoute.params;
        console.log(`Loading post: ${category}/${slug}`);
    }
});

Query Strings

Access and manipulate URL query parameters.

Reading Query Parameters

// URL: /search?q=wildflower&page=2
wildflower.component('search-results', {
    init() {
        const query = window.router.currentRoute.query;
        console.log(query.q);    // 'wildflower'
        console.log(query.page); // '2'

        this.searchTerm = query.q || '';
        this.page = parseInt(query.page) || 1;
    }
});

Navigating with Query Parameters

// Add query parameters to navigation
router.navigate('/search', {
    query: {
        q: 'framework',
        category: 'javascript',
        page: 1
    }
});
// Results in: /search?q=framework&category=javascript&page=1

router.getRouteUrl()

Generate a URL string for a named route without navigating. Useful for building href attributes or constructing URLs programmatically.

Signature

router.getRouteUrl(name: string, params?: object, query?: object, hash?: string): string

Parameters

ParameterTypeDefaultDescription
name string - The name of the route (as defined in route configuration)
params object {} Route parameters to fill in dynamic segments
query object {} Query parameters to append as a query string
hash string '' Hash fragment to append (with or without leading #)

Returns

A URL string. Returns '/' if the named route is not found (and logs an error).

Example

const router = wildflower.createRouter({
    routes: [
        { path: '/users/:id', name: 'user-profile', component: 'user-profile' },
        { path: '/search/:query?', name: 'search', component: 'search-results' }
    ]
});

// Basic URL generation
router.getRouteUrl('user-profile', { id: 42 });
// => '/users/42'

// With query parameters
router.getRouteUrl('search', { query: 'wildflower' }, { page: 2 });
// => '/search/wildflower?page=2'

// Optional parameters are omitted when not provided
router.getRouteUrl('search');
// => '/search'

// With hash fragment
router.getRouteUrl('user-profile', { id: 42 }, {}, 'bio');
// => '/users/42#bio'

Route Guards

Control navigation based on conditions (authentication, permissions, etc.). Guards use a return-based API: return a value to control navigation, no callback needed.

Global Guards

const router = wildflower.createRouter({
    routes: [...]
});

// Before each route change: return-based
router.beforeEach(({ to, from }) => {
    const isAuthenticated = wildflower.getStore('auth').isLoggedIn;

    if (to.meta.requiresAuth && !isAuthenticated) {
        return '/login';   // Redirect
    }
    // Return nothing = allow navigation
});

// After each route change
router.afterEach(({ to, from }) => {
    // Analytics, scroll position, etc.
    analytics.pageView(to.path);
});

Per-Route Guards

const routes = [
    {
        path: '/admin',
        component: 'admin-dashboard',
        meta: { requiresAuth: true, requiresAdmin: true },
        beforeEnter: ({ to, from }) => {
            const user = wildflower.getStore('auth').user;
            if (!user || !user.isAdmin) {
                return '/unauthorized';  // Redirect
            }
            // Return nothing = allow
        }
    },
    {
        path: '/editor',
        component: 'document-editor',
        beforeLeave: ({ to, from }) => {
            const editor = wildflower.getStore('editor');
            if (editor.hasUnsavedChanges) {
                return false;  // Cancel navigation
            }
            // Return nothing = allow
        }
    }
];

Guard Return Values

Return ValueEffect
undefined / true Allow navigation
'/path' (string) Redirect to path
{ path: '/path', query?: {...} } Redirect to path with optional query parameters
false Cancel navigation

Lifecycle Hooks

Hook into the navigation lifecycle.

Router Hooks

const router = wildflower.createRouter({ routes: [...] });

// Before navigation: return-based guard
router.beforeEach(({ to, from }) => {
    console.log('Navigating from', from.path, 'to', to.path);
    // Return nothing = allow
});

// After navigation completes
router.afterEach(({ to, from }) => {
    console.log('Navigation complete');
});

// Navigation errors: listen via DOM event
document.addEventListener('route:error', (e) => {
    console.error('Navigation failed:', e.detail.error);
});

Component Route Hook

Components can respond to route changes via onRouteChange:

wildflower.component('dashboard', {
    // Called after navigation completes and this component is active
    onRouteChange(to, from) {
        console.log('Route changed to', to.path);
        // Refresh data, update UI, etc.
    }
});

DOM Events

The router dispatches CustomEvents on document for external integration:

EventWhenCancelable
route:beforeChangeBefore navigation startsYes
route:afterChangeAfter navigation completesNo
route:redirectWhen a redirect occursNo
route:errorOn navigation errorNo
route:notFoundWhen no route matchesNo

Nested Routes

Define child routes for nested views.

Configuration

const routes = [
    {
        path: '/users/:id',
        component: 'user-layout',
        children: [
            // /users/:id/profile
            { path: 'profile', component: 'user-profile' },
            // /users/:id/posts
            { path: 'posts', component: 'user-posts' },
            // /users/:id/settings
            { path: 'settings', component: 'user-settings' }
        ]
    }
];

Parent Component

<!-- user-layout component provides the wrapper -->
<div data-component="user-layout">
    <nav>
        <a href="/users/123/profile">Profile</a>
        <a href="/users/123/posts">Posts</a>
        <a href="/users/123/settings">Settings</a>
    </nav>

    <!-- Child route components render here -->
    <div data-router-view></div>
</div>

Router Instance

Properties and methods available on the router instance.

Property/MethodTypeDescription
router.currentRoute Route Current matched route object
router.currentRoute.params object Current route parameters
router.currentRoute.query object Current query parameters
router.navigate(path, options?) function Navigate to path (or { name, params, query } for named routes)
router.getRouteUrl(name, params?, query?, hash?) function Generate a URL string for a named route without navigating
router.beforeEach(guard) function Register global before guard: ({ to, from }) => result
router.afterEach(hook) function Register global after hook: ({ to, from }) => {}
router.isActive(pattern, opts?) function Check if pattern matches current route. opts: { exact: true }
router.abortNavigation() function Cancel an in-progress navigation
router.destroy() function Tear down the router and remove event listeners
router.viewTransitionsAvailable boolean Whether browser supports View Transitions API
router.viewTransitionsEnabled boolean Whether transitions are enabled AND supported
router.currentTransition ViewTransition | null Current active transition (during navigation)
router.setViewTransitions(enabled) function Enable/disable view transitions at runtime
router.on(event, callback) function Subscribe to router events (e.g., viewTransitionStart)