Updating

The code is yours once it is in your project, so updates are never automatic: you compare, then choose what to take.

See what changed

The shadcn CLI keeps no record of what it installed. To compare your copy of an item with the registry’s current version:

Terminal

npx shadcn@latest add @snow-ui-pro/<name> --diff

Take the new version

If you haven’t changed the item, replace your copy. Commit first, so the update is one reviewable change:

Terminal

npx shadcn@latest add @snow-ui-pro/<name> --overwrite

If you have changed it, apply the parts of the diff you want by hand, or overwrite and re-apply your edits from version control. Run --dry-run first to see every file the command would write.

New items

New templates and blocks appear in the catalogue as they are released:

Terminal

npx shadcn@latest search @snow-ui-pro

The snow-ui components

The free components a Pro item uses update the same way, from the public registry (@snow-ui/<name> --diff). Compare them as well when you update a Pro item: a new Pro version may rely on a newer snow-ui component.

The updates window

Every licence includes 12 months of updates from the day of purchase: new items and new versions from the registry. When it ends, the registry answers 403 updates_expired. What you installed keeps working and stays yours to use under the licence.