Skip to main content

Overview

Provider errors are thrown by the FrontMCP dependency injection system. They cover unregistered providers, scope mismatches, construction failures, circular dependencies, and plugin dependency issues. All provider errors are internal errors.

Error Reference

ProviderNotRegisteredError

Thrown when a provider token is not found in the registry.
Example:

ProviderScopeMismatchError

Thrown when a provider’s scope doesn’t match the registry it’s being resolved in.

ProviderNotInstantiatedError

Thrown when a provider is expected to be instantiated but hasn’t been created yet.

DependencyCycleError

Thrown when a circular dependency is detected in the provider graph.
Example:

ProviderConstructionError

Thrown when constructing a provider instance fails.
Example:

ProviderDependencyError

Thrown when a provider dependency cannot be resolved.

ProviderScopedAccessError

Thrown when a scoped provider is accessed from the wrong scope.
Example:

ProviderNotAvailableError

Thrown when a provider is not available in the current context.

PluginDependencyError

Thrown when a plugin dependency cannot be resolved.

InvalidDependencyScopeError

Thrown when a dependency has an invalid scope configuration.

InvalidPluginScopeError

Thrown when a plugin with scope='server' is used in a standalone app, which is not allowed.