Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Invalid resolver strategy specified: yyyy
Invalid resolver strategy specified: yyyy
strategy(string)
This means the internal state of the Internal Resolver has been modified, into an invalid value**.**
Check your code where there's an invalid assignment to a resolver strategy, that may look like resolver.strategy = ...
Please also note that this error could be caused by a plugin and not your application. After ruling out that the error is not being caused by your code, try removing any registered plugins one at a time to see if the error resolves itself.
Attempted to jitRegister an intrinsic type: yyyy. Did you forget to add @inject(Key)
Attempted to jitRegister an intrinsic type: yyyy. Did you forget to add @inject(Key)
Interface name
A DI container is trying to resolve an instance of an interface, but there is no registration for it. This means the instance you are trying to load has not been registered with Dependency Injection.
Ensure that you are registering your interface with Aurelia. This can be done inside of the register method on the Aurelia instance or through the DI methods themselves.
Please also note that this error could be caused by a plugin and not your application. After ruling out that the error is not being caused by your code, try removing any registered plugins one at a time to see if the error resolves itself.
Resolver for yyyy returned a null factory
Resolver for yyyy returned a null factory
String version of the key being resolved
No factory was found for transient registration.
This means the transient registration you gave to a container wasn't with a proper factory registered along with it, consider using container.registerFactory(IMyInterface, someFactoryObject) to fix this issue.
Please also note that this error could be caused by a plugin and not your application. After ruling out that the error is not being caused by your code, try removing any registered plugins one at a time to see if the error resolves itself.
yyyy not registered, did you forget to add @singleton()?
yyyy not registered, did you forget to add @singleton()?
Name of the key being resolved
A DI container is trying to resolve a key, but there's not a known strategy for it.
Try adding a strategy for your resolved key. You can do this using @singleton or other forms of DI resolution
Please also note that this error could be caused by a plugin and not your application. After ruling out that the error is not being caused by your code, try removing any registered plugins one at a time to see if the error resolves itself.
Unable to autoregister dependency: [yyyy]
Unable to autoregister dependency: [yyyy]
list of registering parameters
This means during the registration of some value with a container, it has reached the depth 100, which is an extreme case, and is considered invalid.
Check your dependency graph, if it's really complex, which could happen over time, maybe inject a container and resolve the dependencies lazily instead, where possible.
Please also note that this error could be caused by a plugin and not your application. After ruling out that the error is not being caused by your code, try removing any registered plugins one at a time to see if the error resolves itself.
Attempted to jitRegister something that is not a constructor: 'yyyy'. Did you forget to register this resource?
Attempted to jitRegister something that is not a constructor: 'yyyy'. Did you forget to register this resource?
key(any)
This means a container.get(key) call happens without any prior knowledge for the container to resolve the key given. And the container is unable to instantiate this key as it's not a class (or a normal function).
Consider registering the key with the container, or parent or root containers before making the call.
Please also note that this error could be caused by a plugin and not your application. After ruling out that the error is not being caused by your code, try removing any registered plugins one at a time to see if the error resolves itself.
Unable to resolve key: yyyy
Unable to resolve key: yyyy
key(string)
This means a container has failed to resolve a key in the call container.get(key).
This requires specific debugging as it shouldn't happen, with all the default strategies to resolve for various kinds of keys.
Please also note that this error could be caused by a plugin and not your application. After ruling out that the error is not being caused by your code, try removing any registered plugins one at a time to see if the error resolves itself.
Attempted to jitRegister something that is not a constructor: 'yyyy'. Did you forget to register this resource?
Attempted to jitRegister something that is not a constructor: 'yyyy'. Did you forget to register this resource?
key(any)
This means a container.get(key) call happens with key being built in type functions such as String/Number/Array etc.
This could happen from TS generated code where it fails to generate proper metadata, or forgotten registration, consider checking the output of TS when emitDecoratorMetadata is on, or remember to register a resolution for those built-in types.
Please also note that this error could be caused by a plugin and not your application. After ruling out that the error is not being caused by your code, try removing any registered plugins one at a time to see if the error resolves itself.
Cyclic dependency found: name
Cyclic dependency found: name
Name of the key being resolved
Cyclic dependencies found. This means that you have tried including a dependency in your application that is trying to include the dependency you're loading. **** This happens when there is a dependency graph that looks like this: A --> B --> A or A --> B --> C --> A
Check your code and extract what in A that causes the cyclic dependencies into a separate file, and refer to that from both A and B
You can also use a getter and static inject to work around this issue:
Please also note that this error could be caused by a plugin and not your application. After ruling out that the error is not being caused by your code, try removing any registered plugins one at a time to see if the error resolves itself.
Invalid resolver returned from the static register method
Invalid resolver returned from the static register method
This means the internal state of the Internal Resolver has been modified, into an invalid value**.**
Check the register method on the key.
Please also note that this error could be caused by a plugin and not your application. After ruling out that the error is not being caused by your code, try removing any registered plugins one at a time to see if the error resolves itself.
key/value cannot be null or undefined. Are you trying to inject/register something that doesn't exist with DI?
key/value cannot be null or undefined. Are you trying to inject/register something that doesn't exist with DI?
A key was null/undefined in a container.get/.getAll call
Make sure the key is not null/undefined. This sometimes can happen with bundler that leaves circular dependency handling to applications, e.x: Webpack.
Please also note that this error could be caused by a plugin and not your application. After ruling out that the error is not being caused by your code, try removing any registered plugins one at a time to see if the error resolves itself.
yyyy is a native function and, therefore cannot be safely constructed by DI. If this is intentional, please use a callback or cachedCallback resolver.
yyyy is a native function and, therefore cannot be safely constructed by DI. If this is intentional, please use a callback or cachedCallback resolver.
name(string)
A container.invoke(key) or container.getFactory(key) call happens with the key being one of the built-in types like String/Number/Array
Consider avoid using these keys for those calls
Please also note that this error could be caused by a plugin and not your application. After ruling out that the error is not being caused by your code, try removing any registered plugins one at a time to see if the error resolves itself.
Attempted to jitRegister an interface: yyyy
Attempted to jitRegister an interface: yyyy
name(string)
container.get(key) was called with key being an interface with no prior registration
Register the interface with the container before calling container.get().
Please also note that this error could be caused by a plugin and not your application. After ruling out that the error is not being caused by your code, try removing any registered plugins one at a time to see if the error resolves itself.
Cannot call resolve yyyy before calling prepare or after calling dispose.
Cannot call resolve yyyy before calling prepare or after calling dispose.
name(string)
An InstanceProvider.resolve() call happens without having an any instance provided.
Call InstanceProvider.prepare(instance) before resolving, or instantiate the InstanceProvider with an instance in the 2nd parameter.
Please also note that this error could be caused by a plugin and not your application. After ruling out that the error is not being caused by your code, try removing any registered plugins one at a time to see if the error resolves itself.
Resource key "yyyy" already registered
Invalid resolver strategy specified: yyyy
resource key
This means there is a resource with that name already registered with a container
Consider using a different name for the resource (element/attribute/value converter/binding behavior etc...).
Please also note that this error could be caused by a plugin and not your application. After ruling out that the error is not being caused by your code, try removing any registered plugins one at a time to see if the error resolves itself.