Framework initialization cannot find the specified root DOM element. Check that your mount target exists in the HTML before calling wildflower.start().

A component's init() method or setup logic threw an exception. Check the browser console for the underlying error.

Attempting to access a component that doesn't exist in the registry. Verify the component name matches its data-component attribute and that it has been registered.

A component's context object is missing when required. This usually indicates the component was destroyed or not fully initialized.

A parent component's event handler threw an exception when invoked by a child. Check the parent's method for errors.

A computed property function threw an exception during evaluation. Check that all referenced state properties exist and have expected types.

Two or more computed properties reference each other, creating an infinite loop. Restructure your computed properties to break the cycle.

The reactive proxy's set trap encountered an error. This can happen when assigning invalid values or when the state object has been corrupted.

The reactive proxy's delete trap encountered an error when removing a state property.

Failed to read persisted state from localStorage or sessionStorage. The stored data may be corrupted or the storage quota exceeded.

Failed to persist state to localStorage or sessionStorage. Check that the storage quota has not been exceeded and that the data is serializable.

A state update method received an argument of the wrong type. Verify you're passing the correct data type.

Attempting to access a computed property that hasn't been defined. Check the computed block in your component definition.

A computed property was defined as a value instead of a function. Computed properties must be functions that return a value.

A dotted path like user.profile.name contains an invalid segment. Check for typos or undefined intermediate objects.

A user-provided subscription callback threw an exception. Check the function passed to subscribe().

A computed read pool.length or pool.size. Pool aggregates bypass reactivity, so the computed evaluates once and never re-runs when the pool changes, leaving the bound value silently stale. Mirror the count into reactive state inside a tick() instead, e.g. if (this.count !== pool.length) this.count = pool.length;, then bind that state. Dev-mode only; stripped from production builds.

Context data resolution failed during binding evaluation. The bound property path may be invalid or the data structure has changed unexpectedly.

A context operation requires a component instance but none is available. The component may have been destroyed.

The context update process encountered an exception. This is typically caused by invalid data or a corrupted context state.

Failed to notify dependent contexts of a data change. A dependent binding or computed property may have an error.

A data-list element has no <template> child to use as the item template. Add a <template> element inside your list container.

The list rendering process threw an exception. Check that the list data is a valid array and that template bindings reference valid item properties.

Updating an existing list item's bindings failed. The item data may have an unexpected structure.

Removing a list item from the DOM failed. The element may have already been removed or detached.

The optimized append path for adding items to the end of a list encountered an error. The framework will fall back to a full re-render.

The optimized swap path for reordering list items encountered an error. The framework will fall back to a full re-render.

The optimized sparse update path (updating a subset of list items) encountered an error. The framework will fall back to a full re-render.

A data-bind expression failed to evaluate. Check for typos in property names or invalid JavaScript expressions. Also emitted as a warning when store shorthand ($store.path) is used in data-model.

A data-bind-class expression failed to evaluate. Check that the expression returns a valid string or object.

Creating a context for a data-bind-html binding failed. Check that the binding path is valid.

Updating a data-show or data-render conditional context failed. Check that the bound expression evaluates to a boolean-like value.

A data-bind-class binding received a value that is not a string. The element-level path expects a space-separated class string. Inline expressions can use the {'class-name': condition} object form, but a computed property should return the resolved string itself. The framework coerces the value (truthy keys joined to a string, or the value stringified) so the page keeps rendering, but the underlying mismatch should be fixed in your code.

Wrong: computed: { classes() { return { 'is-active': this.active }; } }
Right: computed: { classes() { return this.active ? 'is-active' : ''; } }

A data-action handler method threw an exception. Check the method referenced in your data-action attribute.

A component method execution failed. Check the method for runtime errors such as accessing undefined properties.

emit() was called but the component instance could not be located. Ensure the component is mounted and initialized.

emit() was called but the component's context is unavailable. The component may have been destroyed.

Navigation attempted to access a route that hasn't been defined. Check your route configuration.

A route alias points to a target route that doesn't exist. Verify the alias target matches a defined route path.

A navigation guard function (beforeEnter, beforeLeave, etc.) threw an exception. Check the guard function for errors.

The navigation queue has exceeded its maximum retry attempts. This usually indicates a redirect loop in your route guards.

Navigation by name references a route that doesn't exist. Check the name property in your route definitions.

A route definition has an invalid structure. Routes require at minimum a path property.

Attempting to initialize the router more than once. The router should only be configured and started once per application.

No route pattern matches the requested URL path. Consider adding a catch-all route (path: '*') for 404 handling.

A route's handler function threw an exception during execution.

An async/lazy-loaded route component failed to load. Check the network request and module path.

The scroll restoration or positioning function threw an exception after navigation.

A route lifecycle hook (beforeEnter, afterEnter, etc.) threw an exception.

Server-side rendered component activation failed. The server-rendered HTML may not match the expected component structure.

Hydrating server-rendered HTML encountered an error. Ensure the server-rendered markup matches the client component's expected structure.

wildflower.store() was called with a non-string first argument. The store name must be a string.

wildflower.store() was called with a non-object second argument. The store definition must be a plain object.

A store's init() lifecycle hook threw an exception. Check the store's initialization logic.

The store creation process failed. Check the store definition for structural errors.

external() failed when accessing a store. Verify the store name and property path are correct.

A store subscription callback threw an exception. Check the function passed to the store's subscribe() method.

Automatic creation of the default application store failed. This is an internal initialization error.

The CSP-safe expression parser encountered syntax it cannot parse. Simplify your binding expression or check for syntax errors.

The expression contains a syntax construct not supported by the CSP-safe expression parser. The parser supports literals, identifiers, member access, binary/logical/unary/conditional expressions, array expressions, and function calls. Anything else (arrow functions, template literals, object literals, destructuring, assignment, etc.) triggers this error. Simplify the expression or move the logic into a computed property or component method.

CSP security policy blocked one of: (1) a blocked global identifier (window, document, eval, Function, fetch, setTimeout, and others); (2) a blocked property access (__proto__, prototype, constructor); or (3) a function call other than external(). In CSP mode, only external() is permitted as a function call in binding expressions.

The render effect system failed to resolve a binding path during a reactive update. The bound property may not exist on the component's state.