---
title: MARKLESS_COMPONENT_TAG_UNRESOLVED
description: "Member component tag must come from an import: a Markless compiler error."
sidebar: { hidden: true }
search: { keywords: ["COMPONENT_TAG_UNRESOLVED","component tag unresolved","markless error"] }
pagination: false
---

**Error** from the compiler, while it builds your `.tsrx` files.

## What happened

Markless prints the message, the reason, and a suggestion:

```text
MARKLESS_COMPONENT_TAG_UNRESOLVED: Cannot resolve `<<tagName> />` because `<rootName>` is not imported in this file.
The compiler links a child component to the module it comes from at build time. Without an import it cannot find the component to render, and dropping the tag silently would delete the subtree.
Import the object that holds the component, for example `import * as <rootName> from './<rootName>.tsrx';` or `import { <rootName> } from './<rootName>.ts';`.
https://markless.dev/errors/MARKLESS_COMPONENT_TAG_UNRESOLVED
```

Words in angle brackets change from case to case.

## How to fix it

Start with the suggestion in the message above.

This page has no guide yet. [Help write it](/contributing/improve-these-docs).

## Where it comes from

`@markless/compiler` raises this code. Source:

- [packages/compiler/src/passes/semantic-graph/diagnostics.ts](https://github.com/compiled-run/markless/blob/main/packages/compiler/src/passes/semantic-graph/diagnostics.ts)

Read [how to read a Markless error](/tooling/diagnostics), or go back to [all error codes](/errors).