Documentation Index
Fetch the complete documentation index at: https://docs.nextlovable.com/llms.txt
Use this file to discover all available pages before exploring further.
Common Issues in Version 0.0.6
Authentication Problems
Cannot authenticate / API key rejected
Cannot authenticate / API key rejected
-
Verify API key is correct:
- Log into nextlovable.com
- Go to your dashboard
- Copy the API key exactly (no extra spaces)
-
Re-run authentication:
Paste the API key when prompted
-
Check account status:
- Ensure your account is active
- Verify you have credits remaining
- Check for any billing issues
-
Network connectivity:
Should return a 200 status code
Authentication token expired
Authentication token expired
-
Re-authenticate:
-
Check token storage:
-
Clear stored credentials and re-auth:
Network/firewall issues
Network/firewall issues
-
Check firewall settings:
- Ensure outbound HTTPS (port 443) is allowed
- Whitelist
*.nextlovable.comdomains
-
Corporate proxy:
-
Test connectivity:
Installation Issues
Command not found: next-lovable
Command not found: next-lovable
next-lovable shows “command not found”Solutions:- Restart your terminal - This refreshes the PATH
-
Check installation location:
-
Verify npm global bin is in PATH:
The npm prefix path should be in your PATH
-
Add npm global bin to PATH (if missing):
-
Use npx as alternative:
Version mismatch after installation
Version mismatch after installation
next-lovable --version shows wrong versionSolutions:-
Uninstall and reinstall specific version:
-
Clear npm cache:
-
Check for multiple installations:
Node.js version compatibility
Node.js version compatibility
-
Check Node.js version:
Version 0.0.6 requires Node.js 16.x or higher
-
Update Node.js:
- Visit nodejs.org for official installer
- Or use nvm:
nvm install 18 && nvm use 18
-
For Ubuntu/Debian:
Migration Issues
Source directory not recognized as React project
Source directory not recognized as React project
-
Verify package.json exists and contains React:
-
Check for required dependencies:
-
Install missing dependencies:
- Check project structure: Ensure you have components or pages that use React Router
Migration fails with syntax errors
Migration fails with syntax errors
-
Fix syntax errors first:
-
Common syntax issues in v0.0.6:
- Missing semicolons
- Incorrect JSX syntax
- TypeScript type errors
- Import/export statement issues
-
Simplify complex patterns:
- Break down large components
- Remove experimental JavaScript features
- Fix any linting errors
- Skip problematic files: Move complex files out temporarily, migrate, then manually port them
Target directory creation fails
Target directory creation fails
-
Check permissions:
-
Use different location:
-
Check disk space:
-
Run with elevated permissions if needed:
Migration incomplete / hangs
Migration incomplete / hangs
-
Check network connectivity:
-
Monitor system resources:
-
Try smaller batches:
- Exclude large files temporarily
- Remove node_modules before migration
- Clear any build artifacts
-
Enable verbose logging:
-
Kill and restart:
Post-Migration Issues
Generated Next.js app won't start
Generated Next.js app won't start
npm run dev fails with errorsSolutions:-
Install dependencies:
-
Common dependency issues:
-
Fix configuration issues:
-
Clear cache and rebuild:
Routing doesn't work correctly
Routing doesn't work correctly
-
Check App Router structure:
-
Verify page.tsx exports:
-
Check for client component issues:
-
Review navigation components:
Ensure Link components use
hrefinstead ofto
TypeScript errors after migration
TypeScript errors after migration
-
Update TypeScript configuration:
-
Install missing type definitions:
-
Fix common type issues:
Performance Issues
Migration is very slow
Migration is very slow
-
Check project size:
-
Exclude unnecessary files:
-
Check network speed:
-
System resources:
- Close other applications
- Check available RAM and CPU
- Use faster storage (SSD vs HDD)
High credit consumption
High credit consumption
-
Check project complexity:
- Large projects consume more credits
- Complex routing patterns increase usage
- Many components increase processing
-
Use dry-run to estimate:
This shows estimated credit usage
-
Consider breaking down project:
- Migrate in smaller chunks
- Remove unused components
- Simplify complex routing
- Upgrade to newer version: Version 0.0.7+ offers free single file conversions
Version 0.0.6 Specific Limitations
Workarounds
- For testing small changes: Use online converters or manual conversion
- For better control: Upgrade to version 0.0.7+
- For complex projects: Consider manual migration with v0.0.6 as reference
Getting Help
Debug Information
When reporting issues, include:Support Channels
GitHub Issues
Discord Community
Documentation
Upgrade Recommendation
- Free single file conversions
- Better error handling
- More granular control
- Improved performance
- Enhanced CLI experience
Version 0.0.7+ Features
Migration Guide
Frequently Asked Questions
Can I use v0.0.6 without authentication?
Can I use v0.0.6 without authentication?
Can I undo a migration?
Can I undo a migration?
- Used a separate target directory (recommended)
- Have backups or version control
- Used
--dry-runfirst to understand changes
Why does my complex routing not convert correctly?
Why does my complex routing not convert correctly?
- Custom route guards
- Dynamic route configurations
- Nested routing with complex logic
- Integration with state management
How do I migrate from v0.0.6 to newer versions?
How do I migrate from v0.0.6 to newer versions?
- Uninstall v0.0.6:
npm uninstall -g next-lovable - Install latest:
npm install -g next-lovable - Note: Command structure changed in v0.0.7+
- 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:- Version confirmation:
next-lovable --versionoutput - Clear description of the problem
- Steps to reproduce the issue
- Sample project that demonstrates the issue
- Expected vs actual behavior
- System information (OS, Node.js version, etc.)
