What language support in an IDE is made of
summary
An IDE stack for JavaScript/TypeScript/JSX/TSX: a fast lexer for instant highlighting, a resilient parser that recovers from incomplete code to build an AST, and a project index that skips node_modules to avoid scanning tens of thousands of files. Navigation and completion are driven by indexes plus TypeScript .d.ts files, while type inference uses indexed symbols, call/return analysis and control‑flow/data‑flow graphs to power inspections; supporting TS/TSX and Babel plugins is necessary but often fragile given widespread React and TypeScript usage.
AI-written summary · about
chapters (16)
- 0:00Language support in IDEs
- 1:28Choosing language for IDE support
- 4:46Keyword highlighting with lexer
- 7:38JavaScript lexing challenges
- 10:47Parser builds syntax tree
- 12:35Parsing new language versions
- 15:30Syntax tree for code analysis
- 17:59Code indexing for search
- 20:29Navigation and autocompletion
- 22:15JavaScript autocompletion strategies
- 23:17JavaScript type inference via annotations
- 25:44Type inference and inspection process
- 27:28Control flow graph inspections
- 29:15Data flow analysis for inspections
- 30:18Code optimization via analysis
- 31:21Language support behind the scenes
related talks
40mIntegrating IDEs with Dotty the experimental Scala compiler
44mIntegrating IDEs with Dotty, The Experimental Scala Compiler
46mCompilers, User Interfaces & the Rest of Us
36mCool kids' way of generating code
36mMythical trees and where to find them
44mJavaScript AST programming: Introduction and beyond
27mAST Meta-programming
01h 01mTypescripten: Generating Type-safe JavaScript Bindings for emscripten