Legacy Version: This is version 0.0.6 which requires authentication for all operations. Consider upgrading to version 0.0.7+ for free single file conversions and enhanced features.
What is next-lovable v0.0.6?
A CLI tool that automatically converts your React applications to Next.js 13+ using the new App Router. This legacy version provides full project migration capabilities with API-based processing.
Key Features
Complete Project Migration
Full React to Next.js App Router conversion
Smart Router Conversion
React Router to Next.js navigation transformation
Vite to Next.js Migration
Seamlessly migrates from Vite build system
Intelligent Components
Automatically adds βuse clientβ directives where needed
Get Started
1
Install the CLI
2
Preview your migration
3
Run the migration
Documentation
Installation Guide
Setup and authentication instructions
Quick Start
Your first migration in 5 minutes
Migration Command
Complete command reference
Troubleshooting
Common issues and solutions
Upgrade to v0.0.7+
Enhanced features and free conversions
What You Can Do
Full Project Migration (Authentication Required)
Complete Migration
Convert entire React applications to Next.js
Preview Changes
See exactly what will change before applying
What Gets Converted
React Router β Next.js App Router
React Router β Next.js App Router
useNavigate()
βuseRouter()
fromnext/navigation
<Link to="/path">
β<Link href="/path">
fromnext/link
useLocation()
βusePathname()
anduseSearchParams()
- Route structure converted to app directory
Project Structure
Project Structure
- Vite configuration β Next.js configuration
- Component organization for App Router
- Package.json scripts and dependencies
- TypeScript configuration updates
Component Enhancements
Component Enhancements
- Automatic βuse clientβ directive addition
- Server/client component separation
- Import path optimization
Command Reference
Task | Command | Authentication | Credits |
---|---|---|---|
Preview migration | next-lovable ./app --dry-run | β Yes | β No |
Full migration | next-lovable ./app ./next-app | β Yes | β Yes |
Real-World Example
Version 0.0.6 Limitations
Important Limitations:
- Authentication required for all operations
- Credit consumption for all migrations
- No single file mode - only full project migration
- Limited error recovery compared to newer versions
- Simpler CLI without subcommands
Why Upgrade to v0.0.7+?
Free Features
Single file conversions without authentication
Better CLI
Subcommand structure with more control
Enhanced Performance
Faster processing and better error handling
Granular Control
Choose specific transformations to apply
Migration Path: Existing v0.0.6 users can easily upgrade to the latest version for enhanced features and free single file conversions.
Command Structure
Version 0.0.6 uses a simple command structure:Available Options
--dry-run, -d
- Preview changes without making them--yes, -y
- Skip confirmation prompts--install, -i
- Install dependencies after migration
π§ Prerequisites
1
Node.js 16+
Version 0.0.6 requires Node.js 16.x or higher
2
React Project
A React application using React Router
3
nextlovable.com Account
Required for authentication and API access
4
Active Credits
Migration operations consume credits
Need Help?
Ready to Migrate?
Start with v0.0.6
Use the current legacy version
Upgrade to Latest
Get enhanced features and free conversions
Legacy Support: While v0.0.6 continues to work, we recommend upgrading to version 0.0.7+ for the best experience with free features and enhanced capabilities.
What Gets Converted
React Router β Next.js Router
React Helmet β Next.js Head
Command Comparison Table
Task | Command | Credits Required | Authentication |
---|---|---|---|
Preview project migration | next-lovable migrate ./my-app --dry-run | β | β Yes |
Full project migration | next-lovable migrate ./my-app ./next-app | β Yes | β Yes |
β οΈ Important Notes
Version 0.7+: Uses new subcommand structure (
migrate
, convert
)Version 0.6 and earlier: Uses legacy command formatAlways backup your original project before running a full migration!
Limitations & Best Practices
Known Limitations
- Complex custom route configurations may need manual adjustments
- Dynamic route parameters might require review
- Some third-party integrations may need updates
- Complex state management setups might need fine-tuning
Best Practices
- Always test individual files first using the free
convert
command Run --dry-run
before any actual migration- Keep backups of your original project
- Review generated files before deployment
- Test thoroughly after migration
Getting Help
List Available Commands
Ready to migrate your React app to Next.js? Start with a simple file conversion to see the magic in action! π