Troubleshooting
Solutions for common issues with qmims
This section provides solutions for common issues you might encounter when using qmims. If you're experiencing a problem not covered here, please check the GitHub repository for more information.
Common Issues
Debugging
For detailed debugging information, use the verbose flag:
qmims generate --verbose
This will show:
- Command execution details
- Amazon Q interactions
- File operations
- Error messages with stack traces
Tip
When reporting issues, always include the output from running the command with the
--verbose flag.Checking Dependencies
Many issues with qmims are related to its dependencies. You can check if all dependencies are correctly installed:
# Check Node.js version node --version # Check Amazon Q CLI installation q --version # Check qmims version qmims --version
Make sure you have:
- Node.js version 18.x or later
- Amazon Q Developer CLI installed and authenticated
- qmims installed globally
Getting Help
For command-specific help:
qmims --help qmims generate --help qmims edit --help qmims config --help qmims templates --help
Still Having Issues?
If you're still experiencing problems after trying these solutions, please open an issue on the GitHub repository.
Common Error Messages
| Error Message | Possible Cause | Solution |
|---|---|---|
| Amazon Q Developer CLI is not available | Amazon Q CLI not installed or not authenticated | Install and authenticate Amazon Q CLI |
| ENOENT: no such file or directory | File or directory not found | Check file paths and current directory |
| EACCES: permission denied | Insufficient permissions | Check file permissions or run with elevated privileges |
| Template not found | Template name is incorrect or template doesn't exist | Check template name or add the template |
| Invalid configuration | Configuration file is corrupted | Run qmims config setup to reset configuration |