Writing VS Code extensions for fun and profit
summary
Shows how VS Code extensions actually replace a legacy IDE by wiring TypeScript + Node/npm into tasks.json and launch.json, running 266 npm packages installed to scaffold and debug, using readelf and regex to auto-resolve shared libs and set LD_LIBRARY_PATH for remote debugging. Demonstrates a custom Teru build integration invoked from a tree view, and a useful prototype implemented in about 130 lines of extension code that builds, uploads, and debugs — and it works.
AI-written summary · about
chapters (12)
- 0:00VS Code extensions intro
- 1:05VS Code at C++ conf
- 5:15Why VS Code over others
- 7:42Benefits of extensions
- 10:09First extension tutorial
- 15:16Practical extension in TS
- 25:42Advanced search/replace
- 26:04Legacy IDE replacement
- 31:27Dynamic path resolution
- 39:58Custom build systems
- 43:59Debugging with extensions
- 51:06Closing thoughts
related talks
31mBuild My First VS Code Extension in 25 Minutes Flat
19mBuilding a VS Code Extension
45mDevelopment of VSCode extensions
29mUpgrade Your Toolbox with IDE Extensions
01h 04mWorkshop: Build your First VS Code Extension
30mYour IDE deserves better
16mExtending VS Code, or How to Create Yourself a Back Office in 10 Minutes
30mVS Code Can Do That