Troubleshooting

The CLI prefixes errors with nateui: and skipped-file warnings with warn:. In the message formats below, angle-bracketed values stand for the values the CLI inserts; they are not literal output.

The CLI cannot find a token

Run npx nateui@latest login with the email used for the template purchase when the CLI prints nateui: invalid or missing token — run: nateui login.

Your account needs a template choice

When the CLI prints nateui: pick your template first at https://nateui.com/dashboard, choose a template in the dashboard.

Your account has no active license

If the CLI prints nateui: no active license on this account — see https://nateui.com/pricing, open the pricing page and check the license on your account.

Your license does not cover the template

The access error message format is nateui: your license covers <covered-templates> - '<requested-template>' requires All-Access or its own license (https://nateui.com/pricing). Use a covered template flag from Installation, or follow the pricing link in the error.

The project folder is not empty

If init-template prints nateui: target 'my-app' is not empty, choose another folder or empty that target before running the command.

A page file differs

The skipped-file warning message format is warn: exists, differs, skipped: <file-path> (rerun with --overwrite to replace). It leaves that file unchanged but marks the page installed. A later add-page call uses the message format page '<page-id>' already installed — nothing to do. Use the remove-then-add steps in Getting a newer version to retry.

A config marker is missing

The config marker error message format is nateui: <config-path> is missing the '<marker>' marker — add-page needs it to know where to insert. Restore that exact marker in the named file; Lines not to delete lists the markers in a new starter.

The page ID is unknown

If add-page prints the unknown-page message format nateui: unknown page '<page-flag>' for template '<template>' — run: nateui list --template <template>, run npx nateui@latest list --template <template> from the project root and use a page ID from that template's output.

A new page does not highlight

Make the route key and menu key match in src/configs/routes.config.ts and src/configs/navigation.config.ts.

An import fails after adding a page

If an import fails after add-page, run the install command that the CLI printed from the project root: