How nathantodd-devel/minlang works
minlang is an early-stage language tokenizer with a CLI that reads a source file, tokenizes it, validates the token stream, and prints JSON or formatted errors. Token definitions and schemas support tokenization and a parser scaffold; the CLI does not invoke that parser. The README gives no further product capabilities. The parser’s parse method is empty, and the available excerpts do not establish a larger compilation workflow.
Main entry points: src/index.ts CLI entry · tokenizer/index.ts Tokenizer · tokens.ts Token schemas · errors.ts Lexical errors
Components 11
CLI
- CLI entry
src/index.ts
Tokenization
- Tokenizer
src/tokenizer/index.ts - Lexical errors
src/tokenizer/errors.ts - String utility
src/tokenizer/utils.ts
Language model
- Token schemas
src/tokenizer/tokens.ts - Generic error
src/error/index.ts - Parser scaffold
src/parser/index.ts - Expression schema
src/parser/expression.ts
Other components
- CLI user
- Source file
- Token JSON
Connections 12
- CLI user → CLI entry: invokes
src/index.ts - CLI entry → Source file: reads
src/index.ts - CLI entry → Tokenizer: tokenizes with
src/index.ts - Tokenizer → Token schemas: uses schemas
src/tokenizer/index.ts - Tokenizer → Lexical errors: raises
src/tokenizer/index.ts - Tokenizer → String utility: uses
src/tokenizer/index.ts - Lexical errors → Generic error: extends
src/tokenizer/errors.ts - CLI entry → Token schemas: validates stream
src/index.ts - CLI entry → Token JSON: prints tokens
src/index.ts - CLI entry → Lexical errors: formats errors
src/index.ts - Parser scaffold → Token schemas: validates stream
src/parser/index.ts - Expression schema → Token schemas: uses token schema
src/parser/expression.ts