4 ms·
I went down this route recently. There are a couple of different options depending on your preference: • Write the glue code yourself if you only need svelte o
by banashark 6y ago
I went down this route recently.
There are a couple of different options depending on your preference:
• Write the glue code yourself if you only need svelte on a few pages
• Inertiajs if you want to replace your view layer with svelte
- lexx 6y agoI agree with you. I did give a look at Inertiajs just because Laravel was friendly towards it. Looks sweet. Right now the "glue" I came up with is a silly connection between the server side router and the "Entry" component of Svelte. It works, it's 10 lines of code, it's clean and the website is super fast. But, both Inertia and my solution feel somehow "hackish". Not a proper pattern. But really, anything to avoid client side routing, state management and auto-magic code splitting.
- brainbag 6y agoWow, InertiaJS looks like exactly what I've been wishing for. Component-driven SFCs in Vue are the best tool I've used for interfaces in 20+ years, but I don't love having an API layer between the client and server. This is really interesting. Do you have experience with it and know how it handles frequently live-updating pages?