Skip to content
chant Docs Demo

Lexicon Issues

llms.txt lists every page for an agent
Optional: hand this page to your coding agentThe steps work by hand too.
Show the whole prompt
Read https://intentius.io/chant/troubleshooting/lexicon-issues/.
Diagnose the lexicon error this project shows: check the resource class name for typos, update the lexicon with `npm update @intentius/chant-lexicon-<name>`, and run `npx chant update`.
Run `npx chant build` and `npx chant lint` until both pass, and open a pull request.
Never deploy to a real cloud account or shared environment (with `chant run`, `chant components` or a platform's own CLI), approve (a pull request review, `chant approve` or `chant run approve`), override a policy denial (`chant approve policy-override`), or merge; never cut or publish a release (`chant release cut --yes` or `chant release publish`), push or delete a `ci/*` tag (`chant ci tick` pushes them), or change the value of an existing flag; never touch `.chant/allowed_signers` or `chant/lifecycle`.

Missing Type Declarations

Section titled “Missing Type Declarations”

Symptom: Missing type declarations in your IDE, or import errors.

Fix:

Terminal window
# Sync lexicon type definitions
chant update

chant update syncs lexicon types into .chant/types/.

Unknown Resource Type

Section titled “Unknown Resource Type”

Symptom: Unknown resource type 'X' error during build or lint.

Cause: The resource type isn’t in the installed lexicon. Either the lexicon is outdated or there’s a typo.

Fix:

  1. Check for typos in the resource class name
  2. Update the lexicon package: npm update @intentius/chant-lexicon-<name>
  3. Run chant update

No IDE Autocomplete

Section titled “No IDE Autocomplete”

Symptom: Your editor doesn’t provide autocomplete for resource properties.

Fix:

  1. Run chant update then chant lint --fix to generate types
  2. Verify tsconfig.json is configured correctly (see TypeScript Configuration)
  3. Restart your editor’s TypeScript language server

chant