andrueandersoncs/better-typescript
User repository on GitHub
A modern, agentic, type-aware TypeScript linter built on tsgo and Jev
- Forks
- 0
- Last pushed
- Updated Oct 2026
Repo stats from the GitHub API, cached Oct 2026.
Jev directory
CommunityJev Tools & CLIs
Better TypeScript
A type-aware TypeScript linter that pins a public typescript-go compiler module and runs syntax- and type-aware rules in one AST pass per root file; its semantic mode reads changed files and asks TypeSafe Noul questions over bounded spans and candidates per policy.
- Stars
- 8
- Language
- TypeScript
- License
- MIT
- Reading time
- 2 min
- Published by
- Community
- Author
- andrueandersoncs
- Last verified
- Oct 2026
Used inJev for Software & DevTools
- Languages
- TypeScriptGo
- Platforms
- CLI
- Capabilities
- Open source
Highlights
- A Go linter for TypeScript projects, built on a pinned public typescript-go compiler module.
- Runs all syntax- and type-aware rules in one AST pass per root source file.
- better-typescript semantic reads complete changed, selected, or committed-range files, then asks TypeSafe Noul questions over bounded source spans.
- Question and candidate selection is scoped per policy, per the README.
- MIT licensed TypeScript repo from the author of jev-cli and visual-jev; 8 stars, created 2026-06-10, pushed 2026-10-16.
Quickstart
bash
npm install --save-dev @better-typescript/better-typescript
npx better-typescriptWatch out
README reviewed 2026-10-17; the digest truncates after the install block, so the available policies, Noul configuration, and any accuracy results are not visible. The repo documents itself at andrueandersoncs.github.io/better-typescript, which the digest links but does not capture.
Questions about this entry
Short answers drawn from the linked project or page.
A modern, type-aware TypeScript linter from andrueandersoncs. It is implemented as a Go linter that uses a pinned typescript-go compiler module and runs syntax- and type-aware rules in one AST pass per root source file.
Its semantic mode reads complete changed, selected, or committed-range files and then asks TypeSafe Noul questions over bounded source spans and selected candidates for each policy. The digest does not show how the answers become findings.
Install the package as a dev dependency with npm install --save-dev @better-typescript/better-typescript, then run npx better-typescript. The semantic mode is invoked as better-typescript semantic with a changed, selected, or committed range.
It combines syntax- and type-aware rules in a single AST pass per root file rather than separate lint and type-check phases, and adds a semantic mode backed by typed Noul questions. The digest does not compare its accuracy or speed with those tools.
Complete changed, selected, or committed-range files. It asks Noul questions over bounded source spans and selected candidates scoped per policy, so the model does not see the whole file when a narrow question suffices.
andrueandersoncs, who also publishes jev-cli and visual-jev in the Jev ecosystem. The repository is MIT licensed, TypeScript, with 8 stars, created 2026-06-10 and last pushed 2026-10-16.
None appear in the digest. The README excerpt covers the tool's approach and an install block, and the fuller documentation lives at andrueandersoncs.github.io/better-typescript, which was not captured.
More Jev resources like this
A semantic linter that builds state from Tree-sitter and classifies it against user-defined TypeScript rules using Typesafe's Jev, then turns the classification values into actionable output through per-rule callbacks. The binary bundles its own runtime.
Jev Tools & CLIs#community#github#linter
Community
sedulustech/jintTypeScript
sedulustech/jintTypeScriptRead-only Go CLI that semantically checks your files against your own rules with Jev, locally or in CI, printing text or JSON and caching results between runs.
Jev Tools & CLIs#community#github#go
Community
Alurith/jeffGo
Alurith/jeffGoA single-binary gate for Impatient Programming that fails a pull request when an experienced reviewer would ask for the change to be simplified: it asks Jev about each changed file and tells the coding agent what to fix, with no LLM or parser inside.
Jev Tools & CLIs#community#github#go
Community
tools4imps/qualmGo
tools4imps/qualmGoA CLI that asks Jev which files and declarations answer a repository question, then prints verbatim excerpts for a coding agent to use.
Jev Tools & CLIs#community#typescript#cli
Community
dzhng/jevgrepTypeScript
dzhng/jevgrepTypeScriptA local-first tool from Neatlogs for watching what your AI agent did: it ingests the traces your agent already sends, checks every run, and gives coding agents 23 MCP tools to read, explain, search, compare, and replay runs.
Jev Tools & CLIs#community#github#typescript
Community
neatlogs/neatrootsTypeScript
neatlogs/neatrootsTypeScriptA linter whose rules are plain-English yes/no questions about code — secrets in logs, retry loops that run forever, leaked error messages — answered by TypeSafe's Jev as calibrated probabilities, with output shaped like any other linter.
Jev Tools & CLIs#community#catalog-import#logicrw
Community
ice-hazymoon/jevlintTypeScript
ice-hazymoon/jevlintTypeScriptFrom the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.