using @livewireScriptConfig instead of @filamentScripts

I'm using the tables package in livewire components. I'm using an extra Alpine plugin.

So following the Livewire docs in my app.js i added

import { Livewire, Alpine } from '../../vendor/livewire/livewire/dist/livewire.esm';
Alpine.directive('tooltip', (el) => {
    tippy(el, { content: el.textContent });
});

Livewire.start()

import { Livewire, Alpine } from '../../vendor/livewire/livewire/dist/livewire.esm';
Alpine.directive('tooltip', (el) => {
    tippy(el, { content: el.textContent });
});

Livewire.start()

In order to not get 2 instances of Livewire i need to add

@livewireScriptConfig

@livewireScriptConfig

But now the loading indicator in my searchbar of my table is constantly spinning.

Am i doing something wrong?

Filament•2y ago•

2 replies

Remi Hindriks

using @livewireScriptConfig instead of @filamentScripts

I'm using the tables package in livewire components. I'm using an extra Alpine plugin.

So following the Livewire docs in my app.js i added

import { Livewire, Alpine } from '../../vendor/livewire/livewire/dist/livewire.esm';
Alpine.directive('tooltip', (el) => {
    tippy(el, { content: el.textContent });
});

Livewire.start()

import { Livewire, Alpine } from '../../vendor/livewire/livewire/dist/livewire.esm';
Alpine.directive('tooltip', (el) => {
    tippy(el, { content: el.textContent });
});

Livewire.start()

In order to not get 2 instances of Livewire i need to add

@livewireScriptConfig

@livewireScriptConfig

But now the loading indicator in my searchbar of my table is constantly spinning.

Am i doing something wrong?

using @livewireScriptConfig instead of @filamentScripts

Similar Threads

using @livewireScriptConfig instead of @filamentScripts

Similar Threads

Similar Threads

Similar Threads