Why not use children and loading prop?

[adi-works]

The API of this component doesn't make much sense and induces a lot of boilerplate code. Why not use children like Radix does? see https://www.radix-ui.com/themes/docs/components/skeleton.

[OFK0]

Hi,

I created a pull request about this subject, maybe you could review.

#246

@dvtng

[juanpablob]

The API of this component doesn't make much sense and induces a lot of boilerplate code. Why not use children like Radix does? see https://www.radix-ui.com/themes/docs/components/skeleton.

I second this. Let alone the fact that the approach of doing prop.something || <Skeleton /> is not really feasible in the real world 😅 views are much complex than that. The idea of "put the skeletons inline in your components" is a nightmare idea.

Unfortunately, the Skeleton component from Radix UI Themes is not available standalone and we'll have to port it manually including all the dependencies :(

[Sinan0333]

Hey everyone 👋

I came across this issue while working on improving skeleton loading in React apps. I actually built a package called React Skeletonify
that solves this problem in a dynamic way.

Instead of manually defining skeletons or repeating markup, it automatically generates adaptive skeletons based on your component structure — with full control for excluding tags, customizing animation, and managing global or local configs.

If you’re looking for a more flexible solution, you can check it out here:
🔗 Docs: https://react-skeletonify.sinan-dev.in/
🔗 npm: https://www.npmjs.com/package/react-skeletonify

Would love your feedback or ideas for improvement! 😊