Design a new language in JS: from zero to autocomplete
summary
Claims a workable pipeline: a PeggyJS parser generates an AST, three service APIs (evaluate, validate, autocomplete) run on top, and the whole thing embeds into the Monaco editor with live suggestions. The build includes a basic grammar, a validation engine that uses metadata, caching and partial checks, and an autocomplete strategy that uses fake-marker filling to parse invalid input. The approach is tried twice and yields usable autocomplete and diagnostics by trading strict grammar for validation + autocomplete APIs.
AI-written summary · about
chapters (7)
- 0:00Need for new language
- 2:54Grammar and PEG
- 7:31Building the abstract syntax tree
- 11:50Validation engine
- 17:05Autocomplete features
- 22:19Monaco editor integration
- 24:48Summary & Q&A
related talks
27mParsing, Compiling, and Static Metaprogramming
20mAn Approach to Generate Text-Based IDEs for Syntax Correction based on Syntax Specification
46mSix steps from zero to IDE
01h 29mTooling for the JavaScript Era
29mMy Little Parser: Tooling is Magic
46mWhat even is code? Building a non-code coding interface
28mMaster the art of the AST and take control of your JS
27mEffectively Building Language Tools