Skip to main content

Common Issues in Version 0.0.6

Authentication Problems

Problem: Authentication fails with “Invalid API key” or similar errorsSolutions:
  1. Verify API key is correct:
    • Log into nextlovable.com
    • Go to your dashboard
    • Copy the API key exactly (no extra spaces)
  2. Re-run authentication:
    Paste the API key when prompted
  3. Check account status:
    • Ensure your account is active
    • Verify you have credits remaining
    • Check for any billing issues
  4. Network connectivity:
    Should return a 200 status code
Problem: Previously working authentication suddenly failsSolutions:
  1. Re-authenticate:
  2. Check token storage:
  3. Clear stored credentials and re-auth:
Problem: Cannot connect to authentication serversSolutions:
  1. Check firewall settings:
    • Ensure outbound HTTPS (port 443) is allowed
    • Whitelist *.nextlovable.com domains
  2. Corporate proxy:
  3. Test connectivity:

Installation Issues

Problem: After installation, running next-lovable shows “command not found”Solutions:
  1. Restart your terminal - This refreshes the PATH
  2. Check installation location:
  3. Verify npm global bin is in PATH:
    The npm prefix path should be in your PATH
  4. Add npm global bin to PATH (if missing):
  5. Use npx as alternative:
Problem: next-lovable --version shows wrong versionSolutions:
  1. Uninstall and reinstall specific version:
  2. Clear npm cache:
  3. Check for multiple installations:
Problem: Errors about Node.js version being incompatibleSolutions:
  1. Check Node.js version:
    Version 0.0.6 requires Node.js 16.x or higher
  2. Update Node.js:
    • Visit nodejs.org for official installer
    • Or use nvm: nvm install 18 && nvm use 18
  3. For Ubuntu/Debian:

Migration Issues

Problem: Tool doesn’t recognize your React projectSolutions:
  1. Verify package.json exists and contains React:
  2. Check for required dependencies:
  3. Install missing dependencies:
  4. Check project structure: Ensure you have components or pages that use React Router
Problem: Migration stops due to syntax errors in source filesSolutions:
  1. Fix syntax errors first:
  2. Common syntax issues in v0.0.6:
    • Missing semicolons
    • Incorrect JSX syntax
    • TypeScript type errors
    • Import/export statement issues
  3. Simplify complex patterns:
    • Break down large components
    • Remove experimental JavaScript features
    • Fix any linting errors
  4. Skip problematic files: Move complex files out temporarily, migrate, then manually port them
Problem: Cannot create or write to target directorySolutions:
  1. Check permissions:
  2. Use different location:
  3. Check disk space:
  4. Run with elevated permissions if needed:
Problem: Migration process stops or hangs partway throughSolutions:
  1. Check network connectivity:
  2. Monitor system resources:
  3. Try smaller batches:
    • Exclude large files temporarily
    • Remove node_modules before migration
    • Clear any build artifacts
  4. Enable verbose logging:
  5. Kill and restart:

Post-Migration Issues

Problem: npm run dev fails with errorsSolutions:
  1. Install dependencies:
  2. Common dependency issues:
  3. Fix configuration issues:
  4. Clear cache and rebuild:
Problem: Pages don’t load or routing is brokenSolutions:
  1. Check App Router structure:
  2. Verify page.tsx exports:
  3. Check for client component issues:
  4. Review navigation components: Ensure Link components use href instead of to
Problem: Many TypeScript errors in migrated codeSolutions:
  1. Update TypeScript configuration:
  2. Install missing type definitions:
  3. Fix common type issues:

Performance Issues

Problem: Migration takes an extremely long timeSolutions:
  1. Check project size:
  2. Exclude unnecessary files:
  3. Check network speed:
  4. System resources:
    • Close other applications
    • Check available RAM and CPU
    • Use faster storage (SSD vs HDD)
Problem: Migration uses more credits than expectedSolutions:
  1. Check project complexity:
    • Large projects consume more credits
    • Complex routing patterns increase usage
    • Many components increase processing
  2. Use dry-run to estimate:
    This shows estimated credit usage
  3. Consider breaking down project:
    • Migrate in smaller chunks
    • Remove unused components
    • Simplify complex routing
  4. Upgrade to newer version: Version 0.0.7+ offers free single file conversions

Version 0.0.6 Specific Limitations

Known Limitations in v0.0.6:
  • All operations require authentication and credits
  • No single file conversion mode
  • Limited error recovery options
  • No granular transformation control
  • Older React Router patterns may not convert perfectly

Workarounds

  1. For testing small changes: Use online converters or manual conversion
  2. For better control: Upgrade to version 0.0.7+
  3. For complex projects: Consider manual migration with v0.0.6 as reference

Getting Help

Debug Information

When reporting issues, include:

Support Channels

GitHub Issues

Report bugs specific to v0.0.6

Discord Community

Get help from other users

Documentation

Browse v0.0.6 documentation

Upgrade Recommendation

Consider upgrading to version 0.0.7+ for:
  • Free single file conversions
  • Better error handling
  • More granular control
  • Improved performance
  • Enhanced CLI experience

Version 0.0.7+ Features

See what’s new in newer versions

Migration Guide

Learn how to use the latest version

Frequently Asked Questions

No, version 0.0.6 requires authentication for all operations, including single file conversions. Consider upgrading to 0.0.7+ for free features.
Only if you:
  1. Used a separate target directory (recommended)
  2. Have backups or version control
  3. Used --dry-run first to understand changes
There’s no built-in undo feature in v0.0.6.
Version 0.0.6 has limited support for:
  • Custom route guards
  • Dynamic route configurations
  • Nested routing with complex logic
  • Integration with state management
These require manual migration or upgrading to newer versions.
  1. Uninstall v0.0.6: npm uninstall -g next-lovable
  2. Install latest: npm install -g next-lovable
  3. Note: Command structure changed in v0.0.7+
  4. Read the v0.0.7+ documentation for new features

Report a Bug

Found a bug specific to version 0.0.6? Please report it with:
  1. Version confirmation: next-lovable --version output
  2. Clear description of the problem
  3. Steps to reproduce the issue
  4. Sample project that demonstrates the issue
  5. Expected vs actual behavior
  6. System information (OS, Node.js version, etc.)
Report on GitHub →