live_svelte VS svelte-routing

Bun is an executable as far as I understand. Would it be possible to call Bun code directly from another language with bindings?

For example Erlang (and Elixir) has Native Implemented Functions[0] (NIF) where you can call native code directly from Erlang. Elixir has the zigler[1] project where you can call Zig code directly from Elixir.

Maybe you can see where I'm going with this, but it would be super cool to have the ability to call Javascript code from within Elixir. Especially when it comes to code that should be called on the server and client. I'm the developer of LiveSvelte[2] where we use Node to do SSR but it's quite slow atm, and would be very cool to use Bun for something like this.

In any case Bun is super impressive, keep it up!

[0] https://www.erlang.org/doc/tutorial/nif.html

[1] https://github.com/E-xyza/zigler

[2] https://github.com/woutdp/live_svelte

Remote: Yes (Remote only)

Willing to relocate: no

Technologies: Elixir, Phoenix, Svelte, Django, Python

Résumé/CV: Upon request

Email: [email protected]

GitHub: https://github.com/woutdp

Website: https://wout.space/

Current project: https://github.com/woutdp/live_svelte

Past project: https://geoquest.gg/ (made in SvelteKit)

Full-Stack Web Developer. Looking for Elixir/Phoenix work. 7+ years of professional experience working with various web technologies, mainly Python, Django and Svelte(Kit). Would be open for working with Python/Django/Svelte(Kit). Also open to work on frontend and/or backend only projects. Website refresh/new website projects is also something I'm interested in.

Availability: part-time, +- 25 hours per week or less

Location: Vancouver Canada, Remote

Remote: Yes (Remote only)

Willing to relocate: no

Technologies: Elixir, Phoenix, Svelte, Django, Python

Résumé/CV: Upon request

Email: [email protected]

GitHub: https://github.com/woutdp

Website: https://wout.space/

Current project: https://github.com/woutdp/live_svelte

Past project: https://geoquest.gg/ (made in SvelteKit)

Full-Stack Web Developer. Looking for Elixir/Phoenix work. +7 years of professional experience working with various web technologies, mainly Python, Django and Svelte(Kit). Would be open for working with Python/Django/Svelte(Kit). Also open to work on frontend and/or backend only projects. Website refresh/new website projects are also something I'm interested in.

Hi I'm a Full-Stack Web Developer. Looking for Elixir/Phoenix work. +7 years of experience working with various web technologies, mainly Python, Django and Svelte(Kit). Would be open for working with Python/Django/Svelte(Kit). Also open to just work on frontend and/or backend only projects. Website refresh/new website projects are also something I'm interested in.

Availability: +- 20 hours per week or less, hourly or contract work

- Current project: https://github.com/woutdp/live_svelte

- Past project: https://geoquest.gg/ (made in SvelteKit)

- GitHub: https://github.com/woutdp

- Website: https://wout.space/

- Contact: [email protected]

For very high degree of interactivity I've been working on LiveSvelte which might solve that issue for you. Your other points still stand though.

https://github.com/woutdp/live_svelte

I've been working on LiveSvelte[0] which might answer this in the LiveView example. It integrates LiveView with Svelte and has SSR support by calling Node from within Elixir, I wouldn't call it unholy, it's quite nice :)

Routing is fully handled by Phoenix, and you can get quite fast page transitions with Live Navigation Events. It's just that whenever you need complex frontend state you can offload it to Svelte, while still maintaining that backend interopability, in this case with E2E reactivity.

What's also really nice is that LiveView and Svelte are both very declarative in the way they handle the 'view' layer. And so they map really well onto eachother.

I also wrote a blogpost[1] on the topic.

[0] https://github.com/woutdp/live_svelte

[1] https://wout.space/notes/live-svelte

participated in discussion about the initiative to keep svelte-routing package alive on their github issue: https://github.com/EmilTholin/svelte-routing

So my questions are : Is it possible to have routes inside the MFs ? If yes, should I use something like this (https://github.com/EmilTholin/svelte-routing) even if it's not official svelte support ? I don't really see informations about entry points on the Turborepo doc. I want to be able to work on each MF independantly (I mean see them in the browser in dev mode) but then just serve them as modules for the app shell in prod mode. I imagine this is possible but is it a configuration I need to implement myself with the package.json files or is it about Turborepo ? I read this (https://michalzalecki.com/micro-frontends-module-federation-monorepo/) article about a similar approach with Webpack, but in this article I don't quite see where is the difference between the bundling part of Webpack (wich can be whatever I want Vite for Svelte, Turbo for Next, etc.) and the monorepo handling part. So how/why only one tool (webpack) instead of many others (turborepo + other bundlers) ?

I used https://github.com/EmilTholin/svelte-routing with great success, though it looks like the maintainer has recently stopped maintaining it, and recommending sveltekit.

Still, I'd give try, it looks like people are still using it, and perhaps someone else will pick up the burden of maintenance, since there's clearly a ton of demand: https://github.com/EmilTholin/svelte-routing/issues/236

I'll use SvelteKit in the future but I wanted to learn Svelte with the most basic setup first. I don't want to use SSR anyway. I went with a Vite + Typescript setup and used this router library. It's really simple and did work without any hassle. I love the mindblowing simplicity of Svelte, the tiny builds and the blazing fast dev-server HMR. Coming from React and Vue.

Second point, yes you can add routes. Here is the refence I used: https://github.com/EmilTholin/svelte-routing

Routing: We have a few third party ones such as routify, svelte-spa-router and svelte-routing as well as the clientside routers included in SvelteKit and Sapper.