Vladimir Mityukov

will 2.4.4 work nicely with alpine 3?

Downgraded to Livewire v2.4.4 — now, `@entangle` doesn't work… ```html ``` ```html whereDoesntStartWith('wire:model') ->merge(['class' => 'px-8 h-control-h rounded-sm border border-gray-f2 focus:border-cal-lighter text-cal-lg font-medium transition duration-150 ease-in-out']) }} x-ref="input" /> ```...

Same issue here… All of a sudden

Here's what I did: ``` npm i -D browserify-fs npm i -D node-polyfill-webpack-plugin ``` Add this to webpack.mix.conf: ``` const NodePolyfillPlugin = require("node-polyfill-webpack-plugin") mix.webpackConfig({ plugins: [ new NodePolyfillPlugin(), ], resolve:...

Sorry, is there a solution for this issue at the moment (besides of the unit test added)? Or, is there any other way to apply kind of "default" timezone to...

Thank you! Will it apply my default timezone, or just help to avoid errors?

An update here: Livewire now also supports computed properties via php attributes: ```php // old way: protected function getProjectsProperty() { ... } // Livewire 3's way: #[\Livewire\Attributes\Computed] protected function projects()...

you may probably try to tinker with `fuseOptions` in order to adjust the search behavior https://fusejs.io/api/options.html also, increasing of `searchResultLimit` may be helpful

@bmewburn > intelephense.diagnostics.languageConstraints Thank you for the suggestion, it worked. I have a question, though: is there a "documented way" to find out which certain option helps to disable this...

May I offer a quick suggestion: maybe, add another caster, named like `AsAlwaysFluent::class`? The difference is that the attribute would always be Fluent instance, even if the database has `null`...