Fix Invalid package config error with comprehensive error handling

[konard]

Summary

Fixes the "Invalid package config" error reported in issue #1 by adding comprehensive error handling around the dynamic module loading system.

• Added proper try-catch blocks around use-m module loading
• Added specific error detection for corrupted Node.js package.json files
• Provide clear diagnostic messages and actionable solutions for users
• Added test script to validate error handling logic

Root Cause

The error occurs when use-m tries to resolve Node.js modules and encounters a corrupted package.json file in the global Node.js installation (specifically in /home/gitpod/.nvm/versions/node/v22.18.0/lib/node_modules/yargs-v-17.7.2/package.json). This is a Node.js environment issue, not a bug in the tool itself.

Solution

The fix provides:

1. Graceful error handling - Catches module loading failures and exits cleanly
2. Specific error detection - Identifies the "Invalid package config" issue specifically
3. Actionable guidance - Provides users with clear solutions:
   • Clear npm cache
   • Reinstall Node.js
   • Use a Node version manager like nvm
4. Better user experience - No more cryptic stack traces

Test Results

✅ Script runs successfully when modules load correctly
✅ Provides helpful error messages when use-m loading fails
✅ Detects and handles "Invalid package config" errors specifically
✅ All existing functionality preserved
✅ Syntax validation passes (npm test)

Files Changed

• claude-profiles.mjs - Added error handling around dynamic module loading
• examples/test-error-handling.mjs - Test script to validate error detection logic

Fixes #1

🤖 Generated with Claude Code