svelte-routing VS tanstack.com

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.

Luckily there are many libraries helping out with that and today let's see up close how to setup a form with TanStack Form, the form library in the TanStack ecosystem.

- UI kit (I personally have good experience with React Material UI - https://mui.com/; there is also https://tanstack.com/)

I recently listened to a talk by Tanner Linsley, the creator of TanStack (React Query), about his personal experience in the open-source community. I highly recommend listening to it:

Link - https://tanstack.com/

tanstack router

Svelte doesn't use a virtual DOM and when it compiles, it only targets what you are specifically using it for.

The thing with Svelte is that for a big project (like an SPA) you're going to end up using SvelteKit, because that's where all the development focus is for things like routing etc... and SvelteKit isn't nearly as settled. As in, there aren't developed "patterns" for doing a lot of things yet so it's a lot of trailblazing. There's also some features that are missing and on the roadmap but SvelteKit just hit 1.0 in December (these are usually more obscure things but you will still likely encounter them if you're building something of moderate complexity.)

I still think overall it would be fine to use for a big project, but a year from now I think it will be a much easier choice. Something that is happening right now is a lot of big players in the wider JS ecosystem are transforming from being React specific to framework agnostic:

- NextJS -> Auth.js: https://twitter.com/balazsorban44/status/1603082914362986496

- React Table / React Query -> TanStack Table, TanStack Query: https://tanstack.com/

This has all happened in the last few months. So it's still new, and they're still improving as they move away from being React specific. People rely on those projects. As more move in that direction I think it will become easier and easier.

5: TanStack React

This is where the TanStack comes in. I really hope that the fact that the TanStack has all packages built in a framework-agnostic way will help adoption of non-React libraries over time. Think about it: If you need to fetch some data, render a table and maybe virtualize it - you can do all of that with the TanStack. And if you know how to do this in React, you also already know how to do it in Solid, Svelte or Vue.

Other popular packages in this generation include the tanstack series of packages:

Disclaimer, I'm the founder of AG Grid, however I'm also friends with Tanner. You can see from tanstack.com that AG Grid is both a sponsor but more importantly a partner with TanStack.