Upgrade Your Toolbox with IDE Extensions
summary
Builds a VS Code extension that pings a translations JSON API, maps keys into an autocomplete provider (registered for .ts/.tsx) and surfaces a nested translation Explorer tree of categories → keys → values; scaffolded with Nx generators and bundled with esbuild using TypeScript, ESLint and Prettier. The tree/provider logic is ~40 lines of code, updates live from the backend, runs in the extension development host for debugging, and was later exposed via a language server to reach ~20 JetBrains editors.
AI-written summary · about
chapters (14)
- 0:00Introduction and Dan’s story
- 1:07Why IDE extensions matter
- 2:10VS Code extension basics
- 4:59What is NX and why use it
- 7:51Dan’s problem and solution
- 9:17Scaffolding the extension
- 11:43Adding autocomplete for translations
- 15:13Building the translation explorer
- 21:37From prototype to production
- 22:21Reducing context switching
- 24:49Smoothing out workflows
- 26:56Beyond VS Code with language servers
- 28:41Language server protocol benefits
- 29:01Q&A and closing
related talks
58mWriting VS Code extensions for fun and profit
19mBuilding a VS Code Extension
45mDevelopment of VSCode extensions
31mBuild My First VS Code Extension in 25 Minutes Flat
30mYour IDE deserves better
01h 04mWorkshop: Build your First VS Code Extension
23mThe power of Nx Console
32mThe Future is Soon: Migrating Trace Compass, or any plug-in to a VSCode Extension, for Theia!