Migration Overview
This section contains guides for upgrading between Fanfare SDK versions and migrating between different integration approaches.Migration Guides
| Guide | Description |
|---|---|
| V1 to V2 | Upgrading from SDK v1.x to v2.x |
| React to Solid | Moving from React hooks to Solid widgets |
| Custom to Widgets | Replacing custom UIs with widgets |
| Changelog | Version history and release notes |
Version Compatibility
| SDK Version | Core Package | React Package | Solid Package |
|---|---|---|---|
| 2.x | ^2.0.0 | ^2.0.0 | ^2.0.0 |
| 1.x | ^1.0.0 | ^1.0.0 | N/A |
When to Migrate
Consider upgrading when:- New features - Access to latest distribution types and functionality
- Performance improvements - Better bundle size and runtime performance
- Bug fixes - Resolved issues from previous versions
- Security updates - Critical security patches
- Deprecation warnings - APIs scheduled for removal
Migration Strategy
1. Review Breaking Changes
Before upgrading, review the changelog and breaking changes:2. Update Dependencies
Update all Fanfare packages together:3. Fix TypeScript Errors
After updating, run TypeScript compilation to find breaking changes:4. Test Thoroughly
Test all distribution flows:- Queue entry and admission
- Draw entry and results
- Auction bidding
- Waitlist signup
- Timed release window
- Experience journey flow
5. Monitor Production
After deploying:- Monitor error rates
- Check analytics for conversion changes
- Review user feedback
Getting Help
If you encounter issues during migration:- Check the changelog for known issues and workarounds
- Review TypeScript errors for guidance on API changes
- Search GitHub issues for similar problems
- Contact support for critical migration issues
Deprecation Policy
Fanfare follows semantic versioning:- Major versions (x.0.0) - May contain breaking changes
- Minor versions (0.x.0) - New features, backward compatible
- Patch versions (0.0.x) - Bug fixes only
- JSDoc
@deprecatedtags - Console warnings in development
- TypeScript deprecation notices