Does @livewireScripts directive still need to be included when using @filamentScripts?
The TALL preset base.blade.layout has
@livewireScripts
& @livewireStyles
.
I want to use filament in the front-end, so I've inserted the @filamentScripts
& @filamentStyles
directives.
Have I placed the directives in the correct order?6 Replies
I did this too because if I remove
@livewireScripts
, some components doesn't work, like Tabs
, Wizard
, etc.I think its not needed
I only use
@filament*
https://filamentphp.com/docs/3.x/forms/installation#configuring-your-layoutYou don’t need the livewire directives. They are automatically injected with v3
But if you are adding any alpine components on the front end you will need to use the @livewireScriptConfig directive. https://livewire.laravel.com/docs/installation#manually-bundling-livewire-and-alpine
Laravel
Installation | Laravel
A full-stack framework for Laravel that takes the pain out of building dynamic UIs.
Oh okay, this code was not working :
If I remove the comments it works. And I think
@livewireScriptConfig
is not need either because if I add it then it doesn't work @awcodes : https://filamentphp.com/docs/3.x/notifications/upgrade-guide#javascript-assetsJust read through, the link. And try to understand where it all works and why/if it’s needed in your particular app.