Andreas Reinhold / reiniandClaude Opus 5
fef20a9178
tests / lint (push) Failing after 2m6s
tests / feature (8.4) (push) Successful in 1m3s
tests / feature (8.5) (push) Successful in 1m7s
tests / browser (safari, webkit) (push) Successful in 3m14s
tests / browser (chrome, chromium) (push) Successful in 2m9s
tests / browser (firefox, firefox) (push) Successful in 2m29s
<x-card> (filled, elevated, outlined), <x-list> and <x-list-item> (plain or M3 Expressive's segmented list), <x-divider>, <x-collapse> on <details>, <x-modal> on the native <dialog>, <x-drawer> as a side sheet or list-detail pane, and <x-bottom-sheet> with drag to dismiss. Dialogs and sheets bind to a Livewire flag or id and write back false or null on close, or use the surrounding Alpine scope. Rows open from anywhere on them through data-list-row and data-list-open. DesignGuard now also reports Blade directives written inside a component tag, where they do not compile. Browser test helpers wait for a complete document with Alpine and Livewire running: in Firefox, networkidle alone could return before a repeated visit had loaded. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V9NnLxnPp8vaaurb3Z1MFy
19 lines
594 B
JavaScript
19 lines
594 B
JavaScript
/*
|
|
* Livewire Material — imported once from the application's app.js:
|
|
*
|
|
* import '../../vendor/nonameweb/livewire-material/resources/js/material.js'
|
|
*
|
|
* Alpine ships with Livewire, so these only register onto it (on `alpine:init`). A module
|
|
* script runs before Livewire starts Alpine, and wire:navigate keeps it rather than running
|
|
* it again, so nothing registers twice.
|
|
*/
|
|
import './theme.js'
|
|
import './figure.js'
|
|
import './tooltip.js'
|
|
import './menu.js'
|
|
import './snackbar.js'
|
|
import './rich-tooltip.js'
|
|
import './progress.js'
|
|
import './list-rows.js'
|
|
import './bottom-sheet.js'
|