Skip to content

fix: Cannot find module MODULE_NOT_FOUND error handling#6049

Open
xingzihai wants to merge 1 commit intonektos:masterfrom
xingzihai:fix/issue-6034-module-not-found
Open

fix: Cannot find module MODULE_NOT_FOUND error handling#6049
xingzihai wants to merge 1 commit intonektos:masterfrom
xingzihai:fix/issue-6034-module-not-found

Conversation

@xingzihai
Copy link
Copy Markdown

Fixes issue where act fails with MODULE_NOT_FOUND error when module is not found. This PR adds proper error handling to display a clear error message instead of the cryptic MODULE_NOT_FOUND error.

Issue nektos#6034: When running act with actions that have gitignored 'dist/'
folders (common for TypeScript/JavaScript actions), the main script
file (e.g., 'dist/index.js') is not included in the cloned repository.
This causes a MODULE_NOT_FOUND error when trying to execute the action.

Root cause:
- GitHub Actions uses immutable action packages that include pre-built
  files, or requires maintainers to include 'dist/' in releases
- act clones the git repository which doesn't include gitignored files
- When the main file doesn't exist, Node.js throws MODULE_NOT_FOUND

Fix:
- Add file existence checks before executing node actions (main, pre, post)
- Provide helpful error messages explaining:
  1. The missing file and its expected location
  2. The likely cause (gitignored dist folder)
  3. Suggested resolution (build the action or contact maintainer)
- Check for package.json to provide more specific TypeScript/JS guidance

This change improves user experience by clearly explaining the problem
instead of just passing through the cryptic Node.js MODULE_NOT_FOUND
error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant