Hey! Those components are used for the demo site, and shouldn’t ship or get installed when you install the components in the registry.

None of the ones in the registry should have next as a dependency, please lmk if otherwise

React (vs web components) might be questionable, but Next.js as a hard dependency, for a component library, is just weird.

_Try_ to? Are you serious? We're not taking ambiguity due to phrasing, we're talking straight up not mentioning it on either the front page, on the show all page or even on the page the components button takes you to. Not even on this forum thread. There's barely any text on the front page to change and there are even multiple places you can mention React. You could mention it in the title, e.g. "Open source _React_ UI kit for modern document apps" or you could add it to the second paragraph, e.g. "React components ready to drop into user-facing flows, agents, or internal tools." Not to mention the components page. And given what you use to make the website, how does it take this long to update something this trivial when you are going out of your way to promote it, replying to comments and your other services by proxy?

Also, add either user interactive loading of components or lazy load the demos, the amount of demos murder performance on phones.