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: 
    next-lovable auth
    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: 
    curl -I https://api.nextlovable.com/health
    Should return a 200 status code
Problem: Previously working authentication suddenly failsSolutions:
  1. Re-authenticate: 
    next-lovable auth
  2. Check token storage: 
    # Check if config exists
ls -la ~/.next-lovable/
  3. Clear stored credentials and re-auth: 
    rm -rf ~/.next-lovable/
next-lovable 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: 
    # Set proxy if needed
export HTTPS_PROXY=http://proxy.company.com:8080
next-lovable auth
  3. Test connectivity: 
    ping api.nextlovable.com
curl -v https://api.nextlovable.com

​
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: 
    npm list -g next-lovable
which next-lovable
  3. Verify npm global bin is in PATH: 
    npm config get prefix
echo $PATH
    The npm prefix path should be in your PATH
  4. Add npm global bin to PATH (if missing): 
    # For bash/zsh
echo 'export PATH="$(npm config get prefix)/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc
  5. Use npx as alternative: 
    npx next-lovable@0.0.6 ./my-app
Problem: next-lovable --version shows wrong versionSolutions:
  1. Uninstall and reinstall specific version: 
    npm uninstall -g next-lovable
npm install -g next-lovable@0.0.6
  2. Clear npm cache: 
    npm cache clean --force
npm install -g next-lovable@0.0.6
  3. Check for multiple installations: 
    # Find all installations
find / -name "next-lovable" 2>/dev/null
which -a next-lovable
Problem: Errors about Node.js version being incompatibleSolutions:
  1. Check Node.js version: 
    node --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: 
    curl -fsSL https://deb.nodesource.com/setup_18.x | sudo -E bash -
sudo apt-get install -y nodejs

​
Migration Issues

Problem: Tool doesn’t recognize your React projectSolutions:
  1. Verify package.json exists and contains React: 
    cat package.json | grep -E "(react|react-dom|react-router)"
  2. Check for required dependencies: 
    {
  "dependencies": {
    "react": "^16.8.0 || ^17.0.0 || ^18.0.0",
    "react-dom": "^16.8.0 || ^17.0.0 || ^18.0.0",
    "react-router-dom": "^5.0.0 || ^6.0.0"
  }
}
  3. Install missing dependencies: 
    npm install react react-dom react-router-dom
  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: 
    # Check for TypeScript errors
npx tsc --noEmit

# Check for ESLint errors
npx eslint src/
  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: 
    ls -ld /path/to/parent/directory
touch /path/to/parent/directory/test-file
  2. Use different location: 
    # Try in your home directory
next-lovable ./my-app ~/my-next-app
  3. Check disk space: 
    df -h
  4. Run with elevated permissions if needed: 
    sudo next-lovable ./my-app /opt/my-next-app
Problem: Migration process stops or hangs partway throughSolutions:
  1. Check network connectivity: 
    ping api.nextlovable.com
curl -I https://api.nextlovable.com/health
  2. Monitor system resources: 
    # Check memory usage
free -h

# Check CPU usage
top
  3. Try smaller batches:
    • Exclude large files temporarily
    • Remove node_modules before migration
    • Clear any build artifacts
  4. Enable verbose logging: 
    DEBUG=next-lovable* next-lovable ./my-app
  5. Kill and restart: 
    # Find and kill hung process
ps aux | grep next-lovable
kill -9 <process-id>

# Clean up and retry
rm -rf target-directory
next-lovable ./my-app ./clean-target

​
Post-Migration Issues

Problem: npm run dev fails with errorsSolutions:
  1. Install dependencies: 
    cd migrated-project
npm install
  2. Common dependency issues: 
    # Install missing Next.js types
npm install --save-dev @types/react @types/react-dom @types/node

# Update to compatible versions
npm install next@13 react@18 react-dom@18
  3. Fix configuration issues: 
    # Check next.config.js for syntax errors
node -c next.config.js

# Regenerate if corrupted
rm next.config.js
# Create minimal config
echo "module.exports = {}" > next.config.js
  4. Clear cache and rebuild: 
    rm -rf .next node_modules package-lock.json
npm install
npm run dev
Problem: Pages don’t load or routing is brokenSolutions:
  1. Check App Router structure: 
    # Should have this structure
app/
├── layout.tsx
├── page.tsx (home page)
├── about/
│   └── page.tsx
└── contact/
    └── page.tsx
  2. Verify page.tsx exports: 
    // Each page.tsx should export default
export default function PageName() {
  return <div>Content</div>;
}
  3. Check for client component issues: 
    // Add 'use client' if component uses hooks or event handlers
'use client';

import { useState } from 'react';
// ... rest of component
  4. Review navigation components: Ensure Link components use href instead of to
Problem: Many TypeScript errors in migrated codeSolutions:
  1. Update TypeScript configuration: 
    // tsconfig.json
{
  "compilerOptions": {
    "target": "es5",
    "lib": ["dom", "dom.iterable", "es6"],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": false,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "incremental": true,
    "plugins": [
      {
        "name": "next"
      }
    ]
  },
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx", ".next/types/**/*.ts"],
  "exclude": ["node_modules"]
}
  2. Install missing type definitions: 
    npm install --save-dev @types/react @types/react-dom @types/node
  3. Fix common type issues: 
    // Add proper typing for components
interface Props {
  children: React.ReactNode;
}

export default function Component({ children }: Props) {
  return <div>{children}</div>;
}

​
Performance Issues

Problem: Migration takes an extremely long timeSolutions:
  1. Check project size: 
    du -sh ./my-react-app
find ./my-react-app -name "*.tsx" -o -name "*.ts" | wc -l
  2. Exclude unnecessary files: 
    # Remove build artifacts first
rm -rf node_modules dist build .next
  3. Check network speed: 
    # Test upload speed to API
curl -w "@curl-format.txt" -s -o /dev/null https://api.nextlovable.com/health
  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: 
    next-lovable ./my-app --dry-run
    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: 
# Version information
next-lovable --version
node --version
npm --version

# System information
uname -a

# Project information
ls -la my-react-app/
cat my-react-app/package.json

# Error logs (if available)
cat ~/.next-lovable/logs/latest.log

​
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 →
⌘I