Skip to main content

​
Common Issues

​
Installation Problems

Problem: After installation, running next-lovable shows “command not found”Solutions:
  1. Restart your terminal - This refreshes the PATH
  2. Check if npm global bin is in PATH:
    The npm prefix path should be in your PATH
  3. Add npm global bin to PATH (if missing):
  4. Use npx as alternative:
Problem: Getting permission errors during global installationSolutions:
  1. Configure npm to use a different directory (recommended):
  2. Use sudo (less secure):
  3. Use a Node.js version manager like nvm, which handles permissions better
Problem: Errors about Node.js version being too oldSolutions:
  1. Check your Node.js version:
    You need 18.x or higher
  2. Update Node.js:
    • Visit nodejs.org for official installer
    • Or use a version manager like nvm:
  3. For Ubuntu/Debian:

​
Conversion Issues

Problem: Error reading the file you’re trying to convertSolutions:
  1. Check file path is correct:
  2. Use absolute path:
  3. Check file permissions:
  4. Make sure file extension is supported:
    • Supported: .tsx, .ts, .jsx, .js
    • Not supported: .vue, .svelte, etc.
Problem: Tool reports syntax errors in your React componentSolutions:
  1. Fix syntax errors first:
  2. Check for unsupported syntax:
    • Experimental JavaScript features
    • Non-standard JSX patterns
    • Mixing TypeScript and JavaScript incorrectly
  3. Simplify complex patterns:
    • Extract complex logic to separate functions
    • Break down large components
    • Remove experimental decorators
Problem: The converted code doesn’t work as expectedSolutions:
  1. Use dry-run first to preview:
  2. Apply transformations incrementally:
  3. Check for complex routing patterns:
    • Dynamic routes with complex parameters
    • Nested routing with custom logic
    • Route guards and middleware
  4. Manual review needed for:
    • Custom hooks that depend on React Router internals
    • Complex state management patterns
    • Third-party library integrations
Problem: Component uses client-side features but no directive was addedSolutions:
  1. Manually apply client transformation:
  2. Check for these patterns that need ‘use client’:
    • React hooks (useState, useEffect, etc.)
    • Event handlers (onClick, onChange, etc.)
    • Browser APIs (window, document, localStorage)
    • Third-party client libraries
  3. Add manually if needed:

​
Migration Issues

Problem: Cannot authenticate for full project migrationSolutions:
  1. Check your API key:
  2. Re-authenticate:
    Enter your API key from nextlovable.com dashboard
  3. Verify account status:
    • Log into nextlovable.com
    • Check if your account is active
    • Verify you have credits remaining
  4. Check network connection:
Problem: Full project migration stops with errorsSolutions:
  1. Use dry-run first:
    This identifies issues before making changes
  2. Check for blocking issues:
    • Syntax errors in source files
    • Permission issues with target directory
    • Insufficient disk space
    • Network connectivity issues
  3. Try incremental approach:
  4. Clean up and retry:
Problem: The migrated project has errors when running npm run devSolutions:
  1. Install dependencies:
  2. Check Next.js configuration:
    Look for any obvious configuration issues
  3. Review error messages:
    • Missing dependencies
    • Import path issues
    • TypeScript errors
    • CSS/styling conflicts
  4. Common fixes:

​
Performance Issues

Problem: Converting files or projects takes a long timeSolutions:
  1. Check file size:
    Very large files (>100KB) take longer
  2. Break down large files:
    • Split large components into smaller ones
    • Extract utility functions
    • Separate types and interfaces
  3. Check network (for migrations):
    • Full migrations require API calls
    • Slow internet affects migration speed
    • Use --dry-run for local-only testing
  4. System resources:
    • Close other applications
    • Check available RAM and CPU
    • Use faster storage (SSD vs HDD)
Problem: Tool uses too much memory during conversionSolutions:
  1. Process files individually:
  2. Close other applications to free up memory
  3. Increase Node.js memory limit:
  4. Break down large projects into smaller batches

​
Getting Help

​
Debug Information

When reporting issues, include this information:

​
Log Files

Enable verbose logging for detailed error information:

​
Support Channels

GitHub Issues

Report bugs and feature requests

Discord Community

Get help from the community

Documentation

Browse all documentation

​
Frequently Asked Questions

Short answer: Only if you have backups.Best practices:
  1. Always use --dry-run first
  2. Use --output to save to different location
  3. Commit to git before converting
  4. Use version control to track changes
Some routing patterns are too complex for automatic conversion:
  • Custom route guards
  • Dynamic imports with complex logic
  • Nested routing with conditional rendering
  • Integration with state management libraries
These require manual migration.
The tool focuses on converting React/Router code, not build configurations.For Vite → Next.js migration:
  • Next.js handles most bundling automatically
  • Custom webpack configs may need manual porting
  • Most Vite plugins have Next.js equivalents
Custom hooks using React Router internals need manual conversion:

​
Report a Bug

Found a bug? Please report it with:
  1. Clear description of the problem
  2. Steps to reproduce the issue
  3. Expected vs actual behavior
  4. Sample code that causes the issue
  5. System information (OS, Node.js version, etc.)
Report on GitHub →