Build a bettercomponent ecosystemwith us
The component you wrote may be exactly what someone else's project is missing. Four steps from installing the CLI to publishing, so it can be found among 0.
Four steps to get your component online
Commands are below and ready to copy. Already using Studio? Skip the CLI and publish there.
Prepare the component
Build a Vue / React component and write clear usage docs with a runnable demo. Following the AI Skill spec makes it easiest.
Install the CLI
Install the CompHub CLI with npm, globally or locally. Node 16+ is enough.
Start CompHub
Run the command in the component directory. It registers the project, opens the platform and live-previews locally.
Upload and publish
Fill in the details, screenshot and changelog, then publish. The component appears in the library right away.
More than likes
Real projects shape components in return. An issue from production says more than any self-test.
Grow your impact
Component pages show the author, version and download data. Strong components enter the weekly picks and homepage.
Community collaboration
Your component ends up in real projects. Issues and PRs bring increasingly specific suggestions — you are not alone in maintaining it.
Quality assurance
Complete docs, demos and dependency declarations mean what people download actually runs.
Run through these six before publishing
These are not hard gates; they are the six places most likely to break when someone runs your component.
Checklist
- Component name is globally unique and follows PascalCase / kebab-case
- README documents props, events, slots and a minimal example
- The mini demo uses a fixed design size and does not overflow
- Third-party dependencies are declared in comp.json
- The license is explicit and contains no paid assets
- The screenshot is clear, 16:10 and at least 1200px wide
Maintaining it afterwards
Multiple versions coexist. Users can pin a version; write breaking changes clearly when you publish.
“After putting a component on Comp-Hub, the most rewarding part was seeing how other people use it. Issues from real projects explain more than any self-test.”
— A developer who keeps contributingRecently joined contributors
New components keep landing. You could be next.
Ready to share your component?
Start with the spec, or run one command.