Updates in Figma
What Are Updates?
Whenever we release new features, components, or improvements to shadcnstore, you can download new file from Customer Portal. These updates stay optional, there's no pressure to upgrade, and you won't experience any disruption if you stick with your current version.
Access Your Updates
- Log in to the Customer Portal using the email address you used when purchasing shadcnstore
- Navigate to your Purchases section
- Look for the "Figma Design File" card
- Click the button to access and duplicate the latest shadcnstore Figma file
If you don't remember the email address you used, try using the email you might have used. If that doesn't work, contact us at [email protected] and we'll help you get set up.
How Do the Updates Work?
Understanding Figma Updates
Unlike code repositories, Figma is file-based, not code-based. This means:
- Updates don't install automatically like a software package
- New versions won't appear in your library on their own
- You can't "install" updates with a single action in Figma
The Right Approach
When we publish an update, we recommend copying over any new components you need from the updated version into your existing project. This approach allows you to:
- Selectively incorporate improvements that are most relevant to you
- Keep your customizations safe and untouched
- Avoid disrupting your workflow
About Major Version Updates
When shadcn/ui receives a significant update, we sometimes create a new Figma kit version. Here's what we recommend:
- Stick with your current version for existing projects - updating to a newer major version can be challenging because Figma treats each file separately
- Use new major versions for new projects only - it's much simpler to start fresh with the latest kit than to migrate an old one
If you've customized tokens or added your own components, migration becomes even more complicated. It's best to keep what's working and start fresh with new projects.
Adding New Components to Your Library
When a new shadcnstore update is available, here's how to add the new components to your existing library while preserving your customizations.
Prerequisites
Before you start, make sure you have:
- A Figma account with Pro or Higher plan (required for publishing libraries)
- Your custom shadcnstore library based on an older version of the kit with customizations
- The latest version of the shadcnstore Figma file from your Customer Portal
- The Swap Variables Figma plugin (recommended for managing variables across libraries)
Step-by-Step Guide
Step 1: Open Your Libraries
- Open your custom shadcnstore library file in Figma
- Also open the latest shadcnstore Figma file (from your purchases page) in a separate tab or window
- Publish both the old and new library files if you haven't already (this ensures all components and styles are up to date)
Step 2: Copy New Components
- Select the new components from the new file
- Copy them (Cmd/Ctrl + C)
- Switch to your custom library file
- Paste them (Cmd/Ctrl + V) into the appropriate page or section
Step 3: Add Variables and Styles
- If the new components use variables, copy those variables from the updated file
- Open the Variables panel in your library file
- Add or merge the new variables with your existing ones
- Do the same for any new text or color styles the components use
Step 4: Swap in the updated library
- Open the Figma Assets panel and locate the library currently connected to your project
- Choose the updated shadcnstore library source that contains your new components and tokens
- Review the list of component and style replacements before the swap
- Apply the swap so your design file points to the new library definitions
Step 5: Swap variable definitions
- Open the Swap Variables plugin in Figma
- Select one of the newly added components in your library file
- In the plugin, choose Local Variables
- Run the swap so the component adopts your custom variable definitions
Step 6: Confirm the changes in your projects
- Open a project that uses your custom shadcnstore library
- Look for the new components in the Assets panel
- Place one into the design and confirm it renders with your custom styling
- If any component or token looks off, manually re-link the affected variables or component instances
Key Takeaway
You're in control. Keep your current version, selectively adopt the updates that help your work, and only upgrade to new major versions when starting fresh projects. No surprises, no breaking changes.
Need Help?
If you run into any issues during the update process, reach out to us:
- Email: [email protected]
- Support: [email protected]