Skip to main content
Error classes thrown during ESM package loading. Import them from @frontmcp/sdk:

Overview


EsmPackageLoadError

Thrown when loading an ESM package fails — including network errors, CDN timeouts, and module evaluation failures.

EsmVersionResolutionError

Thrown when the npm registry cannot resolve a version for the given semver range — including network errors, 404s, and no matching version.

EsmManifestInvalidError

Thrown when a package’s default export does not conform to the FrontMcpPackageManifest contract — missing name, version, or invalid primitive arrays.

EsmCacheError

Thrown when a cache operation (read, write, cleanup) fails — typically due to file system permission issues or disk space.

EsmRegistryAuthError

Thrown when authentication to a private npm registry fails — invalid token, expired credentials, or wrong registry URL.

EsmInvalidSpecifierError

Thrown when a package specifier string is malformed — does not match the expected @scope/name@range or name@range pattern.