Provide individual components so we can only add those we need to our projects

[hades200082]

I discussed this with the package author on Reddit a week or so ago but wanted to post it here so it's captured at source.

If this UI library pivoted to providing individual components in a way similar to how shadcn/ui does it for React, it would have a number of benefits.

1. You only include the components you need in your project - This means less deployment bloat which would be a massive plus for WASM
2. If the components are truly part of your project as shadcn/ui does it, then there's no confusion over tailwind config needing to point at the nuget packages directory - the components and associated files would be entirely within your project.
3. It allows us to customise the components for our projects since, once they are added they are just Blazor components like any others in the project.
4. It allows the project author to release new versions of components without adversely affecting projects that might already be using them, making the ongoing maintenance and development of this project much easier.

[desmondinho]

@hades200082, thank you for bringing this up!

I think the biggest challenge would be making existing components more lightweight. Currently, they might be considered "too much" for users who want to extend and customize them. I recently checked out the shadcn/ui components, and they are quite basic in comparison.

Also, I believe I've found the perfect solution to address the second issue. It will be included in v2.0.0, which will be the next release instead of v1.2.0 due to breaking changes. Once I set up a staging environment on Azure, I’ll publish a preview version of v2, allowing everyone to try out LumexUI components with Tailwind CSS v4 support and a much smoother installation process that works seamlessly on any machine.

[hades200082]

a much smoother installation process that works seamlessly on any machine

This is the biggest blocker for me personally right now - while you can do workarounds as documented in other threads and convos, getting a large team to work that way is painful - especially in teams distributed over multiple locations or departments. The impact it has on CI/CD is also not trivial.

That said, I still think that the benefits of moving to a more "per-component" based approach are huge.

[desmondinho]

This is the biggest blocker for me personally right now

I can understand all the headaches related to the current approach. This is going to be fixed in the next release. I have already tried it myself in the LumexUI documentation project. The PR is 90% ready.

That said, I still think that the benefits of moving to a more "per-component" based approach are huge.

I agree. Let's see if this topic will gain traction.

[desmondinho]

Hey @hades200082,

I have just pushed a preview release that supports Tailwind CSS v4 and improves installation process. Please give it a try!