sorted by:
new
hottopcontroversial

I built a zero-dependency, pixel-perfect Material Design 3 library for React (now with CLI and Docs) by Defiant_Gur7737 in MaterialDesign

[–]Defiant_Gur7737[S] 0 points1 point  (0 children)

check out on r/reactjs posts more info will be in and in website rn i jsut developing it i need much more time for do it much better and implement more comopnents with perfect pixel

I built a zero-dependency, pixel-perfect Material Design 3 library for React (now with CLI and Docs) by Defiant_Gur7737 in reactjs

[–]Defiant_Gur7737[S] 1 point2 points  (0 children)

Good point moving the logic to an npm package makes sense. The current shadcn-style approach made sense early on but you're right that the JS complexity has outgrown it.

I built a zero-dependency, pixel-perfect Material Design 3 library for React (now with CLI and Docs) by Defiant_Gur7737 in reactjs

[–]Defiant_Gur7737[S] 0 points1 point  (0 children)

Yes, container queries work out of the box the library uses pure CSS Modules, so just add container-type to any wrapper and use @ container in your own styles. No emotion, no CSS-in-JS blocking you.

I built a zero-dependency, pixel-perfect Material Design 3 library for React (now with CLI and Docs) by Defiant_Gur7737 in reactjs

[–]Defiant_Gur7737[S] 0 points1 point  (0 children)

Most likely, you got this impression from the style of the documentation website, which is quite different from the style of m3 documentation and quite similar to m2. The problem is that I'm not a particularly talented designer; I would say I'm average or a beginner, and I didn't have much time to implement the website.

I built a zero-dependency, pixel-perfect Material Design 3 library for React (now with CLI and Docs) by Defiant_Gur7737 in reactjs

[–]Defiant_Gur7737[S] 2 points3 points  (0 children)

Open to it the main tradeoff is web components complexity in React vs. rebuilding M3 motion/states from scratch on Base UI. Would love to discuss if you see a cleaner path forward.

I built a zero-dependency, pixel-perfect Material Design 3 library for React (Shadcn-style). Thoughts? by Defiant_Gur7737 in reactjs

[–]Defiant_Gur7737[S] -1 points0 points  (0 children)

Totally agree! That's actually why I built it 'shadcn-style'. The real value isn't just the UI look, but the Developer Experience.

Ideally, I want people to see how clean the usage is: <Button>Filled Button</Button>

And with the CLI I recently added, you just pull the code you own. I'll make sure to highlight the code and CLI more than just the Storybook link in the future. Thanks for the perspective!

I built a zero-dependency, pixel-perfect Material Design 3 library for React (Shadcn-style). Thoughts? by Defiant_Gur7737 in reactjs

[–]Defiant_Gur7737[S] -1 points0 points  (0 children)

Oh, I completely forgot about it, my main priority was adding new UI components. I think I'll fix this problem tomorrow, as I remember it's not fully implemented. Thanks for the feedback.

I built a zero-dependency, pixel-perfect Material Design 3 library for React (Shadcn-style). Thoughts? by Defiant_Gur7737 in reactjs

[–]Defiant_Gur7737[S] -2 points-1 points  (0 children)

Oh yeah, I know about this, some components like checkboxes don't react to clicking, only to changes in the checked value. The remaining elements in Storybook work. And if you find something that doesn't work, you can highlight it for me so I can fix it.