> For the complete documentation index, see [llms.txt](https://docs.aurelia.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aurelia.io/developer-guides/error-messages/0001-to-0023/aur0010.md).

# AUR0010

Attempted to jitRegister an intrinsic type: yyyy. Did you forget to add @inject(Key)

### **Error message**

Attempted to jitRegister an intrinsic type: `yyyy`. Did you forget to add @inject(Key)

### **Parameters**

Intrinsic type name

### Error explanation

This error occurs when the DI container tries to automatically register (jitRegister) a value that is a JavaScript intrinsic type (such as `String`, `Number`, `Boolean`, `Array`, etc.).

This usually happens because TypeScript's `emitDecoratorMetadata` emits these types for constructor parameters, but Aurelia's DI cannot resolve them unless you explicitly tell it how, using the `@inject` decorator.

### Common causes

* You have a constructor parameter of type `string`, `number`, etc., and did not use `@inject`.
* You are relying on TypeScript's metadata to infer dependencies, but intrinsic types are not automatically resolvable.

### How to fix

* Use the `@inject` decorator to specify the correct dependency key for intrinsic types.

  ```ts
  import { inject } from 'aurelia';
  @inject(String)
  class MyClass {
    constructor(myString) {
      this.myString = myString;
    }
  }
  ```
* If you do not intend to inject an intrinsic type, check for accidental usage or misconfiguration.

### Debugging tips

* Check the constructor parameters of the class that triggered the error.
* Look for missing or incorrect `@inject` usage.
* Review the stack trace to find the source of the resolution attempt.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aurelia.io/developer-guides/error-messages/0001-to-0023/aur0010.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.