Indicates a component's type bindings have a dependency cycle.
Indicates a component declaration has a dependency cycle. That is, at least one type's provider directly or transitively depends on an instance of itself.
Indicates that a there were multiple bindings for the same type.
Indicates that a there were multiple providers for the same type.
Indicates that Karambit was able to parse component declarations, but still failed to generate an implementation. This likely indicates a bug in Karambit. Consider filling an issue if you see this error scope.
Indicates that a provider declaration was malformed.
Indicates that a scope was used improperly.
Indicates that the TypeScript compiler failed to resolve a dependency type used within a Component.
Indicates that a type necessary to construct a component did not have an associated provider.
No component declarations were found in the input source files. This error may be disabled via configuration.
The most generic failure reason, generally indicating that a declaration used for component generation was malformed.
Represents the high-level reason that a failure occurred.