Blocks
sv-blocks blocks: 100 sections with preview
All 100 blocks sv-blocks publishes, with categories, file counts and licence. The table ranks the sections with the most files and links every block page.
Key points
- 100 blocks in 106 files, with no declared npm dependencies.
- 22 local registry dependencies: the catalogue is a monolith.
- MIT licence, but installs tied to the publisher registry.
sv-blocks publishes 100 blocks in 106 files, almost all single-file. The manifest declares no npm dependencies but lists 22 local registry dependencies: header, logos, marquee and progressive blur live inside the project.
Blocks with the most files
| Block | Registry | Files | Category |
|---|---|---|---|
| integration-cards | sv-blocks | 7 | integration |
| card-decorator | sv-blocks | 1 | card |
| comparator-one | sv-blocks | 1 | comparator |
| contact-one | sv-blocks | 1 | contact |
| contact-two | sv-blocks | 1 | contact |
| content-five | sv-blocks | 1 | content |
| content-four | sv-blocks | 1 | content |
| content-one | sv-blocks | 1 | content |
What this source contains
- Repository: SikandarJODD/cnblocks
- Site: https://sv-blocks.vercel.app
- Licence: MIT (LICENSE file in the SikandarJODD/cnblocks repository)
- Categories: taken from the publisher's manifest, not invented.
When to use it
It pays off when you want a broad, self-contained catalogue with no external packages: a hundred sections and no npm dependency. It does not suit installs from a registry other than the publisher's: local: dependencies will not resolve.
A hundred blocks, local dependencies
The catalogue is built to stay inside the project. Nine headers, a logo collection, card-decorator, marquee and progressive-blur are declared as local: and live in the publisher registry, not on npm. It is a monolith shipped as blocks.
The gain is coherence: headers share the same tokens and primitives, so mounting two creates no style conflicts. The risk is portability: if the registry changes or the domain disappears, installing sections that use local: stops working.
With 100 blocks and 106 files depth is minimal: nearly everything fits in one file. Every section is readable on one screen, but shared parts are not extracted. That is convenient for a prototype and needs a refactoring pass for a product you must maintain.
curl "https://ui.eneawork.it/api/blocks?source=sikandarjodd-cnblocks&limit=8"Three examples from the table: integration-cards, card-decorator, comparator-one; the full inventory is at /blocks. For the counting method read how the block catalogue is built, for the copy-versus-compose comparison read the economics of sections, and for heroes read the shadcn hero guide.
Frequently asked questions
How many blocks does sv-blocks have?
One hundred blocks in one hundred and six files, measured on 1 November 2026: almost every section fits in a single file.
What licence does sv-blocks use?
MIT in the SikandarJODD/cnblocks repository. The catalogue says see source, so confirm it in the LICENSE file.
Which npm dependencies are needed?
None declared. The manifest instead lists 22 local registry dependencies, such as header, logo collection, marquee and progressive blur.
What does a local: dependency mean?
That the component lives in the publisher registry, not on npm. If you install from another registry, the reference does not resolve.
How many headers are there?
Nine header blocks, all sharing the same token base. It is the densest category after the content sections.