Code
How chenglou/pretext is laid out, and where to start for common changes.
There is no import map for this report yet.
Where to start reading
- Repository root
- Repository root
- Likely start-up file
- Likely start-up file
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
Find files for a task
AIAdd support for a new language's line-breaking rules
- Add language-specific break rules to src/line-breaks.ts, imported from Unicode CLDR or ICU data
- Add test cases in harness/cases/*.ndjson with representative text samples
- Run harness/invariants.test.ts to validate against browser engines
Add a new text measurement or layout capability
- Implement core logic in src/measurement.ts or src/analysis.ts
- Export new API from src/layout.ts or src/rich-inline.ts
- Add unit tests in src/layout.test.ts with expected values
- Validate against cross-browser recorded outputs in harness/recordings/
Add a new test corpus or validation case
- Add plain text file with language sample to corpora/ directory
- Create NDJSON case file referencing the corpus in harness/cases/
- Run harness/cli.ts to record browser measurements and compare outputs
- Commit accepted outputs to harness/accepted/ for regression detection
Change the public API
- Check the root package configuration before choosing a workspace or command.
Trace runtime behavior
Add or update tests
Change build or automation
RepoPilot lists up to 500 files, so a file missing here may still exist.
- Files marked “likely” are guessed from their names.
- Some entry points named in the manifest are build output or are missing from the file list, so their source is not shown.