Code from here should work: https://github.com/livewire/livewire/issues/625
Might be fixed, not sure. I never personally had this issue and haven’t seen anything about it recently, but I haven’t been looking for it either.
Issue was closed without fixing the root of the problem, but there are a couple of workarounds. https://github.com/livewire/livewire/issues/528
You will also have problems if you have more than one pagination on a page. Should be a non problem for you specifically if you haven’t already ran into it. If anyone else does, you will have to create your own withPagination trait for each one to get around the query string collision. Or use this: https://github.com/livewire/livewire/pull/738.
I’m sure there’s a lot more to be aware of, but at the end of the day if you aren’t getting any console errors or running into the same problems that others are here or in the github issues, you’re probably fine (I’m not as up-to-date on everything as I used to be). I’d strongly recommend catching the error modals and doing your own form of error handling, especially in the case of the session timing out, but that’s mostly ux stuff and not really breaking anything.
As they say, everything works perfect until you go live. Good Luck.