ImportFailed

ImportFailed is a generic error condition indicating that an attempt to import a module, package, or data resource has failed. It is not tied to a single language and may appear as an exception class, error code, or log message across different systems.

In runtime module systems, ImportFailed may be raised when a dynamic import cannot resolve a path or when a module's exports are incompatible. Build tools and bundlers may report ImportFailed when dependencies cannot be resolved. Data import utilities that load files or datasets may report ImportFailed when the source cannot be read or parsed.

Common causes:

- Missing or misspelled path

- Insufficient file permissions or blocked access

- Network or repository resolution failures

- Version conflicts or circular dependencies

- Syntax errors or incompatible interfaces in the imported module

- Broken cache or corrupted artifacts

Resolution and diagnosis:

- Read the error details and stack trace to identify the source

- Verify the import path, filename case, and extension

- Ensure required dependencies are installed and compatible

- Check permissions, network access, and proxy settings

- Clear caches and retry, or adjust module resolution configuration

Examples:

ImportFailed: Could not load module 'utils/math' from /libs/utils/math.js: ENOENT.

ImportFailed: Dynamic import failed for 'date-parser' due to incompatible export shape.

See also:

- ImportError

- ModuleNotFoundError