Repository navigation
Tags
Tags
fix: reverse order of `--lexer` to name, then file Fixes alecthomas#1193
fix(styles): use kebab-case for style name in Aura Theme variants (al… …ecthomas#1183) ### Description Fixes alecthomas#1182 by correcting the style name to follow existing kebab-case convention
feat(styles): add Aura Theme primary variants (alecthomas#1177) #### Description This PR: Adds a new style based on [Aura Theme](https://github.com/daltonmenezes/aura-theme) #### Assets <img width="1388" height="871" alt="aura-chroma-preview" src="https://github.com/user-attachments/assets/0471c9f7-708b-4e73-a935-1058197d66ef" />
feat: improve tracing
`--trace` now outputs a JSON structure with tracing information, eg.
```
{"lexer":"markdown","state":"root","rule":15,"pos":0,"elapsedMs":0.022875}
{"lexer":"markdown","state":"root","rule":15,"pos":1,"elapsedMs":0.002667}
{"lexer":"markdown","state":"root","rule":15,"pos":2,"elapsedMs":0.001833}
{"lexer":"markdown","state":"root","rule":15,"pos":3,"elapsedMs":0.002166}
{"lexer":"markdown","state":"root","rule":15,"pos":4,"elapsedMs":0.002125}
```
This should generally be much more amenable to analysis, eg. convenient
filtering using jq to help track down hotspots:
```
chroma --trace docs.md 2>&1 > /dev/null | jq 'select(. | .elapsedMs > 0.1)' | less
```
PreviousNext