Review error messages + document them
Open
@sarahxsanders is already working on this.
Since Feb 25, 2026.
- Dominant language
- TypeScript
- Stars
- 197
- Forks
- 51
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 94
Description
Do our error messages make sense? Or are they vague catch alls? Before GA, it wouldn't hurt to take a microscope to them, and also document troubleshooting steps for common issues
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.