reviews block and follows it across every surface it touches.
Blocks are copied, not installed as dependencies.
add writes the block’s source files into your project via the aliases in blocks.json — you own and can edit every file afterwards. Updates are opt-in through diff and add --overwrite. When you outgrow the catalog, build your own block.Goal
Install reviews as a block and see it running everywhere it appears.Install the block
Discover the block
Search the registry and inspect what the block ships before installing:
view lists the block’s files by target (API, admin, vendor) and its dependencies.Install it
blocks.json aliases and prints the block’s post-install instructions — module registration, middlewares, migrations.Run migrations and codegen
The block introduced a reviews module, so generate and run its migrations, then refresh the typed route map:
Verify
- The block’s files exist in your repo under the alias-mapped paths.
- Migrations ran cleanly and the API boots.
- The admin and vendor panels show their reviews pages; the store review endpoints respond.
bunx @mercurjs/cli@rc diff reviewsreports no drift from the registry.
FAQ
What if I've already modified files the block wants to write?
What if I've already modified files the block wants to write?
The CLI asks before overwriting existing files (or force it with
--overwrite). If you’ve customized a page the block also ships, merge by hand — you’re merging source, not resolving package versions.How do I update a block later?
How do I update a block later?
bunx @mercurjs/cli@rc diff reviews shows what changed in the registry since you installed. Take updates with add reviews --overwrite, re-applying any local edits afterwards.