Replies: 3 comments 4 replies
-
Hi @gaby, I do not think that UI libraries should be published through cdn. Mantine exports more than 100 components and 50 hooks, if you want all of them in minified umd bundle it will take 2-3mb to load. When you are using modern tools like Next.js or Vite all unused components will be removed at built time (tree shacking). |
Beta Was this translation helpful? Give feedback.
-
I would argue that MUI is quite big too, and their umd production min file is 494 kB, the development one is 1.72MB Source: https://unpkg.com/browse/@mui/[email protected]/umd/ |
Beta Was this translation helpful? Give feedback.
-
My 5 c on the topic - it would be much easier to experiment with things and create online reproducible examples in JSFiddle and other services if there was a single URL bundle. |
Beta Was this translation helpful? Give feedback.
-
I have been reading the docs for Mantine and can't wait to start using it. One thing I notice compared to other libraries like
MUI
is the lack of docs/support for using Mantine directly from a CDN without installing it.Example Docs: https://mui.com/material-ui/getting-started/installation/
Example Usage: https://github.com/mui/material-ui/tree/master/examples/cdn
Unpkg: https://unpkg.com/
The mantine url would look like this (with a umd directory): https://www.unpkg.com/browse/@mantine/[email protected]/
Example of how
react
looks: https://www.unpkg.com/browse/[email protected]/umd/I would be very helpfull if Mantine added support for unpkg/minimized cdn releases to ease development/introduction into Mantine.
Beta Was this translation helpful? Give feedback.
All reactions