> For the complete documentation index, see [llms.txt](https://docs.omlet.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omlet.dev/cli-and-dashboard/learn-omlet-cli/ensure-data-accuracy.md).

# Ensure data accuracy

After scanning your codebase, you might be informed about possible data issues through the Web app.

<figure><img src="/files/BopxTufC9YUARxrn6X39" alt=""><figcaption></figcaption></figure>

These issues can cause the following symptoms:

* Duplicate components
* Some of the components are tagged as **`external`** but they shouldn't be
* The usage counts of some components are inconsistent

They can happen when:

* Omlet is unable to resolve imports from external packages. For example, if your design system library is used in your application repositories as an external dependency, the CLI will need to map imports from the build to their sources correctly.
* Omlet is unable to resolve your import paths properly if you have aliases in a TSConfig file or bundlers like Webpack, Babel, or Vite.

Omlet tries to detect these automatically, but it might not work for your specific setup.

To resolve imports from external packages or map aliases, you can create **`.omletrc`** file in the root directory of your repository and define **`exports`** or **`aliases`** properties. Follow the below instructions depending on your use case:

* [Exports configuration](/cli-and-dashboard/learn-omlet-cli/config-file/resolve-imports-from-external-dependencies.md)
* [Mapping aliases](/cli-and-dashboard/learn-omlet-cli/config-file/map-aliases.md)

If you have components scanned unnecessarily, such as Storybook stories and test files or duplicate components coming from the `dist` folders, you can prevent the CLI from scanning those components by defining their glob patterns. You can learn more here:

* [Excluding certain components & files](/cli-and-dashboard/learn-omlet-cli/config-file/excluding-certain-components-and-files.md)

You can also follow the Config file tutorial with a sample codebase:

* [Tutorial: Config file](/cli-and-dashboard/learn-omlet-cli/config-file/tutorial-config-file.md)

{% hint style="info" %}
**Need help?**

If you need more help or have questions, feel free to contact us at <support@omlet.dev>.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.omlet.dev/cli-and-dashboard/learn-omlet-cli/ensure-data-accuracy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.