`diff` command antithetical to the point?

[datner]

As the introduction stresses:

This is NOT a component library. It's a collection of re-usable components that you can copy and paste into your apps.

What do you mean by not a component library?

I mean you do not install it as a dependency. It is not available or distributed via npm.

Pick the components you need. Copy and paste the code into your project and customize to your needs. The code is yours.

Use this as a reference to build your own component libraries.

I thought this was a good marriage between headless and styled approaches, starting with a template and making changes is much less mentally taxing than creating from scratch, and much less frustrating than trying to hack a style into a packaged component (and then theres the guest libs, which throw all that out the window and revert to good-ol' pre-styled component from npm.. not sure what was the thought process regarding adding those but I don't have to use what I don't want so I don't care).

the diff command is essentially just an unversioned update mechanism, which also reverts all your customization. This is functionally equivalent to a component library with fancy intermediate steps and a laissez-faire approach to code integrity. There is merit to that, but it seems to contrast the point (that I went away with)..

I assume that this command came about from users who do not care for the self-labelling of the lib and just want a mui that is nextjs flavored and is not mui, but unless this is the canonical way to consume shadcn-ui I think it would be appreciated if the internal contradiction would be addressed in the docs 🙏🏻