Download the PHP package edumicro/daisyblade without Composer

DaisyBlade

Pure Blade + Alpine.js + DaisyUI components for Laravel ERP/CRM interfaces.

No Livewire. No magic. No hidden server roundtrips.

Philosophy

DaisyBlade is the evolution of edumicro/daisylw4, rebuilt without Livewire. The stack is intentionally boring:

• Blade renders structure
• Alpine.js manages local UI state
• Axios handles explicit server calls
• DaisyUI 5 provides the design system

Every server interaction is a plain Laravel controller returning JSON. No protocol overhead, no wire attributes, no object inspector surprises. If something breaks, you know exactly where to look.

Requirements

Installation

The install command will ask whether to publish assets for Vite (recommended) or as a public script tag:

Vite setup

Script tag setup

Component prefix

All components use the dbl prefix:

Component reference

Type 1 — Static (Blade + DaisyUI only)

No JavaScript. Receive props, render HTML.

Type 2 — Interactive local (Alpine, no server calls)

UI state managed by Alpine. No Axios.

Type 3 — Interactive remote (Alpine + Axios)

Receive a load-url or action prop. Call plain Laravel controllers returning JSON.

Usage examples

Static badge

KPI stat card

Node graph (Type 2)

Renders a tree of simulation/workflow nodes with per-event color coding and a detail modal. Each node is an array with id, parent (null for roots), label, status, events[], and optional meta{}.

Event badge colours: end → green, abort → amber, fail → red, no termination → ghost. Accumulator events show acc_value inline. Click any node dot or event badge to open the detail modal.

Data table (Type 3)

Toolbar links — export, print, anything

The toolbar prop adds header links that carry the table's current state (page, search, sort, active filters) to a URL of your choosing:

The component is deliberately format agnostic — it knows nothing about spreadsheets, CSV or PDF. It hands the state over and the URL decides what to build, so a second format is a second array entry, not a change here. Each item takes label, url, an optional icon (a full blade-heroicons component name) and an optional download (defaults to true; set it to false for a link meant to open in the page, like a printable view).

Your endpoint receives the same query params as load-url, so build the query in one place and let both the JSON endpoint and the export use it — otherwise the file people download stops matching what they were looking at.

Declarative form (Type 3)

Repeater field (Type 2)

Each field definition is keyed by key (not name):

The repeater dispatches dbl-repeater-change ({ name, rows }) whenever the rows change, so a parent can react without reaching into its Alpine scope:

decimal — the field type for localised numbers

<input type="number"> is the wrong element wherever the decimal separator is not a dot. When the browser cannot parse what was typed it sanitises value to the empty string, so 0,5 reaches the server as nothing at all — and which browsers do this in which locale is inconsistent, which is worse than failing outright.

'type' => 'decimal' renders type="text" inputmode="decimal": the numeric keypad still comes up on mobile, the text arrives intact, and the backend parses it in its own locale.

default — what a new row starts from

Field definitions take default, and it applies to the first row and to every row add() creates. A default that only reaches the first row is a default the user stops seeing the moment they add a second one:

attrs — raw HTML attributes

Schema-driven components take arrays, so there is no attribute bag to merge into. attrs is the array equivalent, available on form.repeater fields and form.fields:

Values are escaped. Attribute names are validated, and on* handlers are refused — event handlers go through events, which is explicit about executing code.

events — Alpine bindings, per target

events maps a target element to Alpine bindings, merged over the component's own defaults. The path is the binding spec and the leaf is the expression:

Targets are root, row, add and remove. In scope: rows, add(), remove(index), notify() — plus index inside a row.

Dotted keys mean the same thing, so a binding can be pasted straight out of the Alpine docs:

The nesting is what makes overriding work. A leaf replaces the branch below it, so passing ['keydown' => ['enter' => 'mine()']] over a default of keydown.enter.prevent leaves one binding — yours. With flat keys the two would be different keys, both would survive, and both would fire. Declaring the same binding twice, or a handler and modifiers on the same node, throws.

To extend a default rather than replace it, call it: ['add' => ['click' => 'add(); mine()']].

events leaves are executable by design. They are for expressions written by the developer, never for values arriving from outside the application.

Key-value editor (Type 2)

Renders a table of key/value rows with an auto-inferring type selector (num/str/bool/{…}). Serialises to a hidden <input> as JSON.

value accepts a PHP associative array. Types are inferred automatically when the user types; the selector lets them override if needed.

List editor (Type 2)

Chip/tag input for an array of strings. Enter or comma adds a chip; Backspace removes the last one.

Multi-step wizard with localStorage resume

If the user refreshes mid-wizard, their progress is automatically restored from localStorage. The storage key is versioned (product-onboarding_{userId}_v2), so changing schema-version invalidates stale state.

App layout

JSON response contract

All Type 3 components expect controllers to return JSON following this contract:

Laravel's response()->json() + standard validation exceptions handle this automatically if you let them.

Publishing views

To customise any component, publish the views:

Published views in resources/views/vendor/daisyblade/ take precedence over package views. Edit freely — your customisations survive package updates.

Testing

188 tests, 294 assertions. All green.

License

MIT — Eduardo de Vicente / Microvalencia Soluciones Informáticas S.L.