svelte-routing VS svelte-material-ui

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.

Sveltematerialui (SMUI): GitHub: https://github.com/hperrin/svelte-material-ui SMUI is a Svelte wrapper for Material-UI, which is one of the most popular Material Design libraries. It provides a collection of components that follow the Material Design guidelines and can be easily integrated into Svelte projects.

For material UI you can use: https://sveltematerialui.com. It works fine although my experience with it is minimal. For tailwind you can run npx svelte-add tailwindcss.

As I mentioned at the beginning of this article, we’re using Svelte Material UI. To install it in our project, we have to first add it to our dependencies:

I know everyone loves Tailwind; I do too. However, there are too many things we take for granted with Material Design. Try and add a simple Date Picker to a Svelte Project. The Materialify project was abandoned (as well as the potential re-write SvelterialJS). The Svelte Material UI hasn't been updated in months, has poor documentation, and may well be on its way to be abandoned as well. Angular Material is well supported by Goodle, React MUI is in the process of getting updated, and so is Vuetify. SolidJS just built a translator for React MUI, and I think it is buggy and doesn't support Solid Start yet. Vercel should donate $$ monthly to support Svelte Material UI. It also needs to add components outside of Material Web (like Datepicker) that the Vue, Angular, and React alternatives support. Material UI is the standard for a reason. Another option would be to find a good translator like Mitosis, but I don't see that happening in this case. That being said, there are some alpha and beta UI Frameworks worth looking at like Skelton and SvelteUI (based on Tailwind). https://sveltematerialui.com/ https://www.skeleton.dev/ https://www.svelteui.org/

The issues I've seen with SMUI have to do with TypeScript support (example), but these should be solved in the upcoming release 7.0.

HI all! I am looking for a good Material UI framework to use with Sveltekit! I have been trying to use SMUI from sveltematerialui.com, however it seems to cause tons of issues and the github issues don't seem to want to fix many of them, it seems like it isn't fully prod ready. I have looked at materialify, it seems good, however it hasn't been updated in the past 12 months, so I am not sure about the status of that. Option 3 would be me making all styles myself.... but that is quite a bit of work and I would like to have something working before the end of the month. Does anyone have any good alternatives to these? I have looked into Google's material libs, but they seem geared towards react and I am not sure if I want to mix things up that much. There must be matieral only CSS libs around that will play well with Tailwind, but I haven't had much luck finding anything (open source) that works well.

I'm using SMUI- the Svelte Material UI inspired by the design on Google sites and Android.

Although this could also be done with some other framework like React, Vue, Svelte, etc.I think using a variant of the MaterialUI with its various widgets (user interface elements that can be used to build your app) will give you the look and feel you are looking for, see https://mui.com/ for React or https://sveltematerialui.com/ for Svelte