# Mapping aliases

{% hint style="info" %}
Make sure to create the **`.omletrc`** file in the root directory of your repository before getting started.
{% endhint %}

If you have alias set up in a **`tsconfig`** file or a bundler such as Webpack, Vite, or Babel, Omlet may have trouble resolving import paths from aliases out of the box. Omlet can resolve them if you define these aliases in the config file.

If you have a **`tsconfig`** file already, you can simply point to it using the **`tsconfigPath`** field:

{% code title=".omletrc" lineNumbers="true" %}

```javascript
{
  ...
  "tsconfigPath": "tsconfig.frontend.json"
}
```

{% endcode %}

If you have alias setup in a bundler, you can define mapping between your aliases and paths in the **`aliases`** field:

{% code title=".omletrc" lineNumbers="true" %}

```javascript
{
  ...
  "aliases": {
    "@components/*": ["src/components/*"],
    "@icons": ["src/icons/index.tsx"]
  }
}
```

{% endcode %}

If your project is a monorepo with multiple packages, you can define package-specific **`aliases`** configurations using the **`workspaces`** field. Such as:

<pre class="language-json" data-title=".omletrc" data-line-numbers><code class="lang-json">{
<strong>  "workspaces": {
</strong><strong>    "@acme/design-system": {
</strong><strong>      "aliases": {
</strong><strong>        "@components/*": ["src/components/*"],
</strong><strong>        "@icons": ["src/icons/index.tsx"]
</strong><strong>      }
</strong><strong>    }
</strong><strong>  }
</strong>}
</code></pre>

You can check the [Config file](https://docs.omlet.dev/cli-and-dashboard/learn-omlet-cli/config-file/broken-reference) documentation to learn more about the **`aliases`** property.