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.

Store API

Complete reference for WildflowerJS global stores.

Stores provide shared reactive state across components without prop drilling. They follow the same patterns as components but exist without a DOM element.

wildflower.store()

Creates a global reactive store that can be accessed from any component.

Signature

wildflower.store(name: string, definition?: StoreDefinition): Store

Parameters

ParameterTypeDescription
name string Unique identifier for the store
definition StoreDefinition Store configuration (state, computed, methods, etc.). Optional; omit to retrieve an existing store.

Returns

The store instance. If the store already exists, the existing instance is returned (the definition is ignored).

Create or get: wildflower.store('cart') with one parameter returns the existing store, equivalent to wildflower.getStore('cart'). With two parameters, it creates the store if it doesn't exist.

Example

const userStore = wildflower.store('user', {
    state: {
        name: 'Guest',
        email: '',
        isLoggedIn: false,
        preferences: {
            theme: 'light',
            notifications: true
        }
    },

    computed: {
        greeting() {
            return this.isLoggedIn
                ? `Welcome back, ${this.name}!`
                : 'Please sign in';
        },

        initials() {
            if (!this.name) return '?';
            return this.name
                .split(' ')
                .map(n => n[0])
                .join('')
                .toUpperCase();
        }
    },

    // Methods at top level (same as components)
    login(name, email) {
        this.name = name;
        this.email = email;
        this.isLoggedIn = true;
    },

    logout() {
        this.name = 'Guest';
        this.email = '';
        this.isLoggedIn = false;
    },

    setTheme(theme) {
        this.preferences.theme = theme;
    },

    init() {
        // Optional: Called when store is created
        console.log('User store initialized');

        // Load persisted state
        const saved = localStorage.getItem('user');
        if (saved) {
            const data = JSON.parse(saved);
            Object.assign(this.state, data);
        }
    }
});

Store Definition

Stores use the same definition pattern as components.

Structure

wildflower.store('store-name', {
    // Reactive state
    state: { /* ... */ },

    // Derived values
    computed: { /* ... */ },

    // Type validation (dev builds)
    types: { /* ... */ },

    // State change watchers
    watch: { /* ... */ },

    // localStorage persistence
    storageKey: 'my-store',  // Enables localStorage persistence
    autoSave: true,          // Auto-save state on every change

    // Called when store is created
    init() { /* ... */ },

    // Called when store is destroyed
    destroy() { /* ... */ },

    // Animation/polling loop (called each frame with delta time)
    tick(dt) { /* ... */ },

    // Custom methods - at top level
    methodName() { /* ... */ },
    anotherMethod() { /* ... */ }
});

Definition Keys

KeyTypeDescription
state object Reactive state properties. Accessed via proxy (e.g., store.count not store.state.count).
computed object Derived values that auto-update when dependencies change.
types object Type validation for state properties (dev builds only).
watch object State change watchers. Same syntax as components: watch: { propName(newVal, oldVal) { ... } }
storageKey string Enables localStorage persistence for store state. The state is saved/loaded using this key.
autoSave boolean When true, automatically saves state to localStorage on every change. Requires storageKey to be set.
init() function Lifecycle hook called when the store is created. Use for setup, loading persisted data, etc.
destroy() function Lifecycle cleanup hook called when the store is destroyed. Use for clearing intervals, releasing resources, etc.
tick(dt) function Animation/polling loop method, called each animation frame with delta time in seconds. Enables headless animation patterns where the store drives updates via requestAnimationFrame.
methods function Custom methods defined at the top level of the definition (not inside an actions block).

Key Differences from Components

FeatureComponentsStores
DOM Element Has this.element No element (DOM-less)
Props Receives props from parent No props
Lifecycle init, destroy, onUpdate, tick init, destroy, tick
Scope Instance per DOM element Singleton - one instance globally

Complete Example

wildflower.store('cart', {
    state: {
        items: [],
        discount: 0,
        currency: 'USD'
    },

    types: {
        discount: 'number',
        currency: 'string',
        items: 'array'
    },

    computed: {
        itemCount() {
            return this.items.reduce((sum, item) => sum + item.quantity, 0);
        },

        subtotal() {
            return this.items.reduce(
                (sum, item) => sum + (item.price * item.quantity),
                0
            );
        },

        total() {
            const sub = this.subtotal;
            return sub - (sub * this.discount / 100);
        },

        isEmpty() {
            return this.items.length === 0;
        }
    },

    watch: {
        items() {
            // Persist cart to localStorage
            localStorage.setItem('cart', JSON.stringify(this.items));
        }
    },

    // Methods
    addItem(product, quantity = 1) {
        const existing = this.items.find(i => i.id === product.id);
        if (existing) {
            existing.quantity += quantity;
        } else {
            this.items.push({ ...product, quantity });
        }
    },

    removeItem(productId) {
        const index = this.items.findIndex(i => i.id === productId);
        if (index > -1) {
            this.items.splice(index, 1);
        }
    },

    updateQuantity(productId, quantity) {
        const item = this.items.find(i => i.id === productId);
        if (item) {
            item.quantity = quantity;
        }
    },

    clear() {
        this.items = [];
        this.discount = 0;
    },

    applyDiscount(percent) {
        this.discount = Math.min(100, Math.max(0, percent));
    },

    init() {
        // Restore cart from localStorage
        const saved = localStorage.getItem('cart');
        if (saved) {
            this.items = JSON.parse(saved);
        }
    }
});

wildflower.getStore()

Retrieves a store instance by name. When used in computed properties, automatically tracks dependencies.

Signature

wildflower.getStore(name: string): Store | null

Parameters

ParameterTypeDescription
name string Name of the store to retrieve

Returns

The store instance, or null if not found.

Automatic Dependency Tracking: When getStore() is called inside a computed property, the framework automatically detects store property access and registers the component as a dependent. The computed property will re-evaluate when the accessed store data changes.

Example

// Get the store
const userStore = wildflower.getStore('user');

// Access state via proxy
console.log(userStore.name);
console.log(userStore.isLoggedIn);

// Access computed (also via proxy)
console.log(userStore.greeting);

// Call methods
userStore.login('Alice', 'alice@example.com');
userStore.logout();

// Modify state via proxy (triggers reactivity)
userStore.preferences.theme = 'dark';

In Computed Properties (Automatically Reactive)

wildflower.component('stats-display', {
    computed: {
        // Automatically reactive - no manual subscription needed!
        totalItems() {
            return wildflower.getStore('cart').items.length;
        },

        // Access store computed properties
        cartTotal() {
            return wildflower.getStore('cart').total;
        },

        // Access nested properties
        userName() {
            return wildflower.getStore('auth').user?.name || 'Guest';
        }
    }
});

In Component Methods

wildflower.component('login-form', {
    state: { email: '', password: '' },

    async handleSubmit() {
        const response = await this.authenticate();
        if (response.success) {
            // Update global store
            const userStore = wildflower.getStore('user');
            userStore.login(response.user.name, response.user.email);
        }
    },

    async authenticate() {
        // API call...
    }
});

$storeName.path (Template Shorthand)

Access store data directly in HTML templates using the $ prefix. Works in all data-* attributes.

Syntax

$storeName.path

Examples

<!-- Bind to store state -->
<span data-bind="$user.name"></span>

<!-- Conditional visibility -->
<div data-show="$auth.isLoggedIn">Welcome back!</div>

<!-- Store-backed lists -->
<div data-list="$cart.items" data-key="id">
    <template>
        <div data-bind="name"></div>
    </template>
</div>

<!-- Nested paths -->
<span data-bind="$auth.user.address.city"></span>

<!-- In expressions -->
<div data-bind-class="$auth.isLoggedIn ? 'online' : 'offline'"></div>
<div data-show="$cart.items.length > 0">Cart is not empty</div>

subscribe: {} (Component Block)

Declaratively subscribe to store changes in your component definition. Enables this.stores auto-injection and onStoreUpdate() callbacks.

Signature

subscribe: {
    [storeName: string]: string[]  // Array of paths to subscribe to
}

Description

Add a subscribe block to your component definition to:

  • Enable this.stores - automatic store injection
  • Receive onStoreUpdate() callbacks when subscribed paths change
  • Automatically clean up subscriptions when component is destroyed

Example

wildflower.component('cart-summary', {
    state: { itemCount: 0, total: 0 },

    // Subscribe to cart.items and cart.discount
    subscribe: {
        cart: ['items', 'discount'],
        user: ['preferences']
    },

    init() {
        // this.stores.cart and this.stores.user are now available
        this.updateFromStore();
    },

    onStoreUpdate(storeName, path, newValue, oldValue) {
        if (storeName === 'cart') {
            this.updateFromStore();
        }
    },

    updateFromStore() {
        this.itemCount = this.stores.cart.items.length;
        this.total = this.stores.cart.total;
    }
});
Note: The paths in the subscribe array are the top-level state properties to watch. For nested properties like user.profile.name, subscribe to 'profile' - you'll receive the entire profile object when any nested property changes.

this.stores

Auto-injected object containing references to stores declared in the subscribe block.

Type

this.stores: {
    [storeName: string]: Store  // Store instances
}

Availability

Available in:

  • init() and all lifecycle hooks
  • All component methods
  • Computed properties

Example

wildflower.component('user-menu', {
    subscribe: {
        auth: ['user', 'token'],
        cart: ['items']
    },

    computed: {
        userName() {
            return this.stores.auth.user?.name || 'Guest';
        },

        cartCount() {
            return this.stores.cart.itemCount;
        }
    },

    logout() {
        this.stores.auth.logout();
    },

    addToCart(product) {
        this.stores.cart.addItem(product);
    }
});

Accessing Store Properties

// Access state
this.stores.auth.user
this.stores.cart.items

// Access computed properties
this.stores.auth.isAuthenticated
this.stores.cart.total

// Call store methods
this.stores.auth.login(email, password)
this.stores.cart.clear()
Requirement: this.stores is only available when you declare a subscribe block. Without it, use wildflower.getStore() instead.

onStoreUpdate()

Lifecycle hook called when a subscribed store path changes.

Signature

onStoreUpdate(
    storeName: string,
    path: string,
    newValue: any,
    oldValue: any
): void

Parameters

ParameterTypeDescription
storeName string Name of the store that changed
path string The subscribed path that changed
newValue any The new value
oldValue any The previous value

Example

wildflower.component('order-status', {
    state: {
        status: 'pending',
        lastUpdate: null
    },

    subscribe: {
        order: ['status', 'items'],
        notifications: ['messages']
    },

    onStoreUpdate(storeName, path, newValue, oldValue) {
        console.log(`${storeName}.${path} changed:`, oldValue, '→', newValue);

        if (storeName === 'order' && path === 'status') {
            this.status = newValue;
            this.lastUpdate = new Date();

            // Show notification on status change
            if (newValue === 'shipped') {
                this.showShippingNotification();
            }
        }

        if (storeName === 'notifications' && path === 'messages') {
            // New messages arrived
            const newCount = newValue.length - (oldValue?.length || 0);
            if (newCount > 0) {
                this.playNotificationSound();
            }
        }
    },

    showShippingNotification() { /* ... */ },
    playNotificationSound() { /* ... */ }
});
Best Practice: Use onStoreUpdate() for side effects (sounds, notifications, analytics). For simple state synchronization, computed properties that read from this.stores are often cleaner.

store.subscribe()

Subscribe to changes on a specific store property.

Signature

store.subscribe(
    path: string,
    callback: (newValue: any, oldValue: any) => void,
    options?: { immediate?: boolean, once?: boolean }
): () => void

Parameters

ParameterTypeDescription
path string Property path to watch
callback function Called when the value changes
options object Optional. immediate: true fires the callback immediately with the current value. once: true automatically unsubscribes after the first change.

Returns

An unsubscribe function. Call it to stop receiving updates.

Example

const userStore = wildflower.getStore('user');

// Subscribe to a property
const unsubscribe = userStore.subscribe('isLoggedIn', (isLoggedIn, wasLoggedIn) => {
    if (isLoggedIn && !wasLoggedIn) {
        console.log('User just logged in!');
        analytics.track('login');
    } else if (!isLoggedIn && wasLoggedIn) {
        console.log('User just logged out');
        analytics.track('logout');
    }
});

// Later: stop listening
unsubscribe();

In Component Lifecycle

wildflower.component('notifications', {
    state: { messages: [] },

    init() {
        const store = wildflower.getStore('notification-store');

        // Store unsubscribe for cleanup
        this.unsubscribe = store.subscribe('messages', (messages) => {
            this.messages = messages;
        });
    },

    destroy() {
        // Clean up subscription
        if (this.unsubscribe) {
            this.unsubscribe();
        }
    }
});

Multiple Subscriptions

wildflower.component('dashboard', {
    subscriptions: [],

    init() {
        const authStore = wildflower.getStore('auth');
        const settingsStore = wildflower.getStore('settings');

        // Track all subscriptions
        this.subscriptions.push(
            authStore.subscribe('user', this.handleUserChange.bind(this)),
            settingsStore.subscribe('theme', this.handleThemeChange.bind(this)),
            settingsStore.subscribe('language', this.handleLanguageChange.bind(this))
        );
    },

    destroy() {
        // Unsubscribe from all
        this.subscriptions.forEach(unsub => unsub());
    },

    handleUserChange(user) { /* ... */ },
    handleThemeChange(theme) { /* ... */ },
    handleLanguageChange(lang) { /* ... */ }
});

Store Methods

Custom methods defined in the store for encapsulating business logic.

Defining Methods

wildflower.store('todos', {
    state: {
        items: [],
        filter: 'all' // 'all' | 'active' | 'completed'
    },

    computed: {
        filteredItems() {
            switch (this.filter) {
                case 'active':
                    return this.items.filter(t => !t.done);
                case 'completed':
                    return this.items.filter(t => t.done);
                default:
                    return this.items;
            }
        },

        activeCount() {
            return this.items.filter(t => !t.done).length;
        }
    },

    // Methods at top level
    addTodo(text) {
        this.items.push({
            id: Date.now(),
            text,
            done: false,
            createdAt: new Date()
        });
    },

    removeTodo(id) {
        const index = this.items.findIndex(t => t.id === id);
        if (index > -1) {
            this.items.splice(index, 1);
        }
    },

    toggleTodo(id) {
        const todo = this.items.find(t => t.id === id);
        if (todo) {
            todo.done = !todo.done;
        }
    },

    setFilter(filter) {
        this.filter = filter;
    },

    clearCompleted() {
        this.items = this.items.filter(t => !t.done);
    },

    // Async methods work too
    async syncWithServer() {
        const response = await fetch('/api/todos');
        const serverTodos = await response.json();
        this.items = serverTodos;
    }
});

Calling Store Methods

// From anywhere
const todoStore = wildflower.getStore('todos');
todoStore.addTodo('Learn WildflowerJS');
todoStore.toggleTodo(123);
todoStore.setFilter('active');

// From component methods
wildflower.component('add-todo-form', {
    state: { text: '' },

    submit() {
        if (this.text.trim()) {
            wildflower.getStore('todos').addTodo(this.text);
            this.text = '';
        }
    }
});

Common Patterns

Authentication Store

wildflower.store('auth', {
    state: {
        user: null,
        token: null,
        isLoading: false,
        error: null
    },

    computed: {
        isAuthenticated() {
            return !!this.token && !!this.user;
        }
    },

    async login(email, password) {
        this.isLoading = true;
        this.error = null;

        try {
            const response = await fetch('/api/login', {
                method: 'POST',
                headers: { 'Content-Type': 'application/json' },
                body: JSON.stringify({ email, password })
            });

            if (!response.ok) throw new Error('Login failed');

            const data = await response.json();
            this.user = data.user;
            this.token = data.token;

            localStorage.setItem('token', data.token);
        } catch (error) {
            this.error = error.message;
        } finally {
            this.isLoading = false;
        }
    },

    logout() {
        this.user = null;
        this.token = null;
        localStorage.removeItem('token');
    },

    init() {
        const token = localStorage.getItem('token');
        if (token) {
            this.token = token;
            this.fetchUser();
        }
    },

    async fetchUser() {
        if (!this.token) return;

        try {
            const response = await fetch('/api/me', {
                headers: { 'Authorization': `Bearer ${this.token}` }
            });
            this.user = await response.json();
        } catch {
            this.logout();
        }
    }
});

Theme Store

wildflower.store('theme', {
    state: {
        mode: 'light', // 'light' | 'dark' | 'system'
        accentColor: '#007bff'
    },

    computed: {
        effectiveMode() {
            if (this.mode === 'system') {
                return window.matchMedia('(prefers-color-scheme: dark)').matches
                    ? 'dark'
                    : 'light';
            }
            return this.mode;
        },

        isDark() {
            return this.effectiveMode === 'dark';
        }
    },

    watch: {
        mode(newMode) {
            localStorage.setItem('theme-mode', newMode);
        }
    },

    setMode(mode) {
        this.mode = mode;
        document.documentElement.setAttribute('data-theme', this.effectiveMode);
    },

    toggle() {
        this.setMode(this.isDark ? 'light' : 'dark');
    },

    init() {
        const saved = localStorage.getItem('theme-mode');
        if (saved) {
            this.mode = saved;
        }
        document.documentElement.setAttribute('data-theme', this.effectiveMode);
    }
});