esm-cjs-risk-scan

Identifying npm dependencies that fail at runtime due to ESM/CJS incompatibility in Electron requires scanning project code for import patterns and probing package.json for module types to highlight potential loading failures. This Skill automates that dependency risk auditing process.

The best way to audit Node dependency risks before upgrading an Electron environment is to evaluate project source directories for npm packages loaded via require() or import(). This process detects packages prone to load failure due to module type mismatches.

Yes, the dependency risk scanner offers scope flexibility to evaluate either specific Electron source directories or all Node-related project files. It examines code for import patterns to ensure comprehensive dependency management and runtime stability.

Yes, you can use this tool to check package.json for module types and exports during dependency management. It probes package.json configurations alongside scanning project files for import patterns to identify ESM/CJS mismatches that may cause runtime loading issues.

Node packages encounter runtime loading issues after an Electron dependency upgrade due to ESM/CJS mismatches. When project code uses require() or import() on incompatible npm packages, the module loading fails at runtime, requiring automated risk analysis to identify and resolve these conflicts.