svelte-material-ui VS vite

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

I am currently utilizing Vite:

Homepage: https://vitejs.dev/

Without any adding any dependencies you can connect react props to raw css at runtime with nothing but css variables (aka "custom properties"). If you add CSS modules on top you don't have to worry about affecting the global scope so components created in this way can be truly modular and transferrable. I use this with vite.

Little confused as to why it has vite in it‘s name, it seems unrelated to https://vitejs.dev/

it says in their docs that they recommend Vite https://vitejs.dev/

it goes like this.

1. you create a repo folder, you cd into it.

2. you create a client template using vite which can be plain typescript, or uses frameworks such as react or vue, at https://vitejs.dev/guide/

3. you cd in that client directory, you npm install, then you npm run dev, it should show you that it works at localhost:5173

4. you follow the instructions on your url, you do npm install @web3modal/wagmi @wagmi/core @wagmi/connectors viem

5. you follow the further instructions.

> It seems like this is for npm or yarn to pull from a remote repository maintained by @wagmi for instance. But then what?

you install the wagmi modules, then you import them in your js code, those code can run upon being loaded or upon user actions such as button clicks

> Do I just symlink to the node_modules directory somehow? Use browserify? Or these days I'd use webpack or whatever the cool kids are using these days?

no need for those. browserify is old school way of transpiling commonjs modules into browser-compatible modules. webpack is similar. vite replaces both webpack and browserify. vite also uses esbuild and swc under the hood which replaces babel.

> I totally get how node package management works ... for NODE. But all these client-side JS projects these days have docs that are clearly for the client-side but the ES2015 module examples they show seem to leave out all instructions for how to actually get the files there, as if it's obvious.

pretty much similar actually. except on client-side, you have src and dist folders. when you run "npm run build" vite will compile the src dir into dist dir. the outputs are the static files that you can serve with any http server such as npx serve, or caddy, or anything really.

> What gives? And finally, what exactly does "browserify" do these days, since I think Node supports both ES modules and and CJS modules? I also see sometimes UMD universal modules

vite supports both ecmascript modules and commonjs modules. but these days you'll just want to stick with ecmascript which makes your code consistently use import and export syntax, and you get the extra benefit of it working well with your vscode intellisense.

> In short, I'm a bit confused how to use package management properly with browsers in 2024: https://modern-web.dev/guides/going-buildless/es-modules/

if people want plain js there is unpkg.com and esm.sh way, but the vite route is the best for you as it's recommended and tested by the providers of your modules.

> And finally, if you answer this, can you spare a word about typescript? Do we still need to use Babel and Webpack together to transpile it to JS, and minify and tree-shake, or what?

I recommend typescript, as it gives you better type-safety and better intellisense, but it really depends. If you're new to it, it can slow you down at first. But as your project grows you'll eventually see the value of it. In vite there are options to scaffold your project in pure js or ts.

First you have to know that all those react projects are created using Vite, and for each of them, you need change the vite.config.ts file by adding the following configuration:

CSSHooks works with React, Prereact, Solid.js, and Qwik, and we’re going to use Vite with the React configuration. First, let's create a project called css-hooks and install Vite:

JavaScript React Flowbite Tailwind Firebase - Auth, Database, and Hosting Vite

For this full-stack single-page app, you'll use Vite.js as your frontend build tool and the react-beautiful-dnd package for draggable items.

Vite