Download the PHP package lyra-ds/blade without Composer

Lyra Blade Components

Thin Blade wrappers for the Lyra Design System in Laravel applications. Each component renders the same canonical .lyra-* classes as its React counterpart—all appearance lives in @lyra-ds/styles, never in this Composer package.

The package ships 42 static and 30 interactive anonymous Blade components under the lyra namespace. Laravel discovers its service provider automatically, so components are ready to use with the short syntax (<lyra:button>) or the equivalent namespaced syntax (<x-lyra::button>).

Quickstart

1. Install the Blade package

2. Install the styles and fonts

Follow the @lyra-ds/styles font setup to load Plus Jakarta Sans and JetBrains Mono in your application.

3. Import the styles once

With Vite, import the package from your JavaScript entry point, usually resources/js/app.js:

Alternatively, import the CSS export from your application's stylesheet:

lyra-ds/blade ships no CSS. The styles package is the single source of appearance for both the Blade and React components.

4. Render your first components

Component props and ordinary HTML attributes can be combined. For example, this input renders its label and validation message while passing name, type, and autocomplete to the underlying input:

Components

Use each name with either equivalent form—for example, button becomes <lyra:button> or <x-lyra::button>.

Component notes & limitations

• Dropdown disabled items (lyra-ds/lyra#289): Items marked with 'disabled' => true render with aria-disabled="true". Under @lyra-ds/alpine 1.1.0, arrow-key roving tabindex does not skip disabled items (they still receive focus). Activation is inert (click, Enter, and Space are swallowed before dispatching lyra:select or navigating), and disabled links drop their href. Visual disabled styling is applied inline pending a dedicated rule in @lyra-ds/styles.

Documentation API artifact

docs/api.json describes every component in this package: its props, a curated usage snippet, the HTML that snippet actually renders, and the name of the Alpine factory that animates it. It is generated by php bin/generate-docs-api, committed to the repository, and attached to every GitHub release, so a consumer can fetch it with gh release download --repo lyra-ds/blade --pattern api.json.

The artifact is consumed by lyra-ds.dev, which uses it to render the Blade tab of the documentation. Treat its field names as a public contract: renaming one breaks the site, so open that change in the site repository as well.

Nothing in it is written by hand. The props come from each @props directive, the usage snippet from resources/docs-examples/<slug>.blade.php, the HTML from rendering that snippet, and values only from the class-emission fixtures—absent observation is an empty list, never a guess. A freshness test fails the suite whenever the committed artifact drifts from the sources, exactly as it does for the Boost guidelines.

components is sorted by slug, binding is null for static components, rootXData is owned for interactive Alpine components (passthrough otherwise), and default is null when the prop is required. Ids that the components derive from uniqid() are replaced by stable id1, id2… placeholders so the artifact is byte-identical across runs.

Class parity with React

Every component emits exactly the class strings emitted by the corresponding Lyra React component. Data-driven class-emission tests enforce that contract using the fixtures in tests/Fixtures/class-emission/, keeping Blade and React on the same styling surface.

Class parity is not the same as full coverage. One React component has no Blade equivalent:

• CreateWorkspaceDialog is a composition, not a primitive: it is dialog plus fields this package already ships. Build it in your application rather than importing a fixed arrangement of them.

React's ThemeProvider and ToastProvider also have no matching tag, because a provider is not a Blade shape. Their behavior is here: the theme lives in @lyraThemeScript plus the Alpine $store.theme, and the toast queue lives in toast-stack.

Compatibility

These are the versions the respective lyra-ds/blade releases were tested against.

Laravel 11 is not supported because it reached security end-of-life in March 2026.

Upgrading from 0.10.x? See the Migration Guide.

Versioning

lyra-ds/blade follows Semantic Versioning with independent SemVer from @lyra-ds/styles, @lyra-ds/react, and @lyra-ds/alpine. See VERSIONING.md for the complete versioning policy, declared public API surface, deprecation process, and migration guarantees.

Releasing

Conventional commits drive the changelog in the bot-maintained release PR. Merge that PR to cut a release; the resulting tag triggers Packagist through its GitHub webhook. Review the compatibility matrix above for every release. See VERSIONING.md for details on release coordination and breaking change requirements.

Interactivity

The Alpine-backed components are accordion, app-sidebar, bottom-sheet, calendar, calendar-view, code-block, combobox, command-palette, cookie-banner, create-workspace-dialog, data-table, date-picker, date-range-picker, dialog, drawer, dropdown, file-manager, file-upload, popover, recurrence-selector, segmented-control, sidebar-group, slot-picker, table-of-contents, tabs, time-input, time-picker, time-zone-picker, toast-stack, tooltip, weekly-schedule-editor, and workspace-switcher. They get their behavior from the @lyra-ds/alpine plugin. Alpine.js >=3.13 <4 is a consumer-installed peer and is never bundled. calendar-view and create-workspace-dialog require @lyra-ds/alpine 1.2.0 or later.

Static components continue to work without Alpine. Alpine-backed components are static-first: except for the data-driven regions described below, their structure and initial state are present in the served HTML and remain inert until Alpine starts.

Some repeated content is intentionally runtime-rendered because filtering, locale-aware generation, queue state, or user-added rows belong to the Alpine binding. calendar, calendar-view, combobox, command-palette, file-upload, time-picker, toast-stack, and weekly-schedule-editor stamp those grids, options, items, toasts, or rows through x-for; those repeated regions do not exist in the served DOM until Alpine boots.

FileUpload controlled lifecycle (breaking change)

file-upload follows the controlled upload lifecycle of @lyra-ds/alpine 1.x and @lyra-ds/styles 1.x (Alpine 0.6/1.0 contract). Your application owns items and the transport; the component never simulates progress or completion.

• Root gets a unique id (yours, or a generated lyra-upload-…) and the dropzone is a <label> for a sibling <input type="file">.
• Selection is proposed through the bubbling lyra:file-upload:select event. Echo proposedItem into your items, upload, and commit uploading/success/error. Retry, cancel and remove are the lyra:file-upload:retry|cancel|remove events. Forward them with x-on: on the component and bind x-model to your items array.
• Statuses: selected, uploading, canceling, success, canceled, error; progress is {kind: 'indeterminate'} or {kind: 'determinate', value}.
• New props: id, name, disabled, required, items, messages (Alpine message overrides with {name}, {percent}, {accept}, {maxSizeMB}), statusLabels, cancelLabel, retryLabel.
• Removed props: defaultItems (use items), uploadDuration, doneLabel; status done (use success), numeric item.progress, remove(id), and .lyra-upload__bar-fill/.lyra-upload__check. removeLabel is replaced by messages.remove.

data-table keeps sorting server-side by default: its header controls emit lyra:sort, and the application returns the rows in the requested order. Set clientSort to opt into in-browser sorting; sortable cells then provide their comparison value through data-sort-value.

After installing @lyra-ds/styles as described in the Quickstart, install Alpine.js and the Lyra plugin:

Then register the plugin before starting Alpine in resources/js/app.js:

Theme

Place @lyraThemeScript in the document <head>, before stylesheets that use theme tokens. It emits a blocking inline script that applies the stored Lyra theme before the first paint; the Alpine theme store takes over after it starts.

The optional storage key is declared in one place—the directive argument—and the Alpine store reads it from the <html data-lyra-theme-key> attribute written by the script. Without an argument, the key defaults to lyra-theme; alternatively, declare data-lyra-theme-key on the <html> element in your layout and keep the argumentless directive.

Toggle between the resolved light and dark themes through the Alpine store:

Add this required rule to your application's CSS:

The styles package does not ship this rule. Without it, closed menus and dialogs can flash before Alpine boots.

Livewire is a first-class integration. Twenty-five components expose controllable state through x-modelable:

• open: bottom-sheet, command-palette (overlay mode), create-workspace-dialog, dialog, drawer, dropdown, popover, and workspace-switcher
• selected: calendar, date-picker, date-range-picker, time-input, and time-picker
• value: combobox, recurrence-selector, and segmented-control
• Component-specific state: accordion (openItems), app-sidebar (collapsed), data-table (selected, or sorting via x-modelable), file-manager (view, with query modelable on its search field), file-upload (items), slot-picker (date, or timezone via x-modelable), table-of-contents (activeId), tabs (active), and weekly-schedule-editor (value, or exceptions via x-modelable)

Use wire:model or x-model directly on a component tag for its root modelable state. Where alternatives are listed, select the target with the x-modelable attribute.

Requirements

• PHP 8.3 or later
• Laravel 12 or 13

Contributing

See CODE_OF_CONDUCT.md.

License

This package is open-sourced software licensed under the MIT License.