Skip to content

Ricy's self-use UI components library, purely focus on frontend

Notifications You must be signed in to change notification settings

Ricy137/Custom-ui

Repository files navigation

Custom-ui

on-going projects, codes're frequently changing The most valuable part of the repo is the README and src/components folder.

Why do I start the repo?

React components libraries like MUI, ANTD is a good option for fast development phase, but they're also large and hard to customize. So I developed custom-ui since a customized component library will provide the minizest size which is good for performance, it will also be much easier for me to customize these components as well as optimize them and it would be a good way to level up my skills as a frontend engineer.

But work is stressful and in high speed. Fortunately, I managed to get some optimization time for a project and successfully replaced all the MUI components with self made components in that project, which recuded almost 20% of overall JavaScript bundle size (of course which also leads to better performance). I decided to make more advantages of these components and make them more reusable, so I started this repo.

Words after developing the project for a while

The original goal of the library is to be highly customizable, include common compoents&interactions and be general (can be used like Apis). However, in my real work, I met different needs for the same component in different projects, it's hard to find a one for all solution, or develop one component library for all projects. So I gradually have the idea that the ability of developing and designing the component library is more important than the component library itself. I would still develop the project, but I also started writing my thoughts while coding, you can read more about it here: https://app.t2.world/article/clrv1kk0j3836220mcwgtkgmbv (currently, this is the only article now).

Conflicts and thoughts

Next: I love Next, the server side rendering is a great way to improve performance, its optimiztion for images is great, turboPack... But of course, due to Next's SSR feature, I also met many conflicts.

One of the conflicts I met is UnoCSS which is an alternative to TailWind. UnoCSS can not only provide better performance and flexsibility, but also released more potention of Atom CSS : https://antfu.me/posts/reimagine-atomic-css . However, UnoCSS doesn't support SSR :( . Current UnoCSS CLI is used.

About

Ricy's self-use UI components library, purely focus on frontend

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published