When Your Extension's Event Bus Becomes a Silent Dependency Hell
You know that sinking feeling. You're refactoring a VS Code extension—maybe one you inherited, maybe your own from six months ago—and you change an ev...
8 articles in this category
You know that sinking feeling. You're refactoring a VS Code extension—maybe one you inherited, maybe your own from six months ago—and you change an ev...
You're in a code review. Someone added a setTimeout to defer extension activation by 50ms. The PR title says 'Improve startup performance.' But the re...
You've been shipping features fast. Real fast. But now your IDE extension takes half a second longer to start, autocomplete sometimes misses, and test...
You're building IDE extensions that need to talk to each other. Maybe you've got a language server passing diagnostics to a UI extension, or a debug a...
You shipped an IDE extension. Users love it. Then you add a plugin system so they can customize it further. Suddenly, every update breaks three commun...
Your extension worked fine in dev. Then users started complaining about janky autocomplete, frozen panels, or the whole IDE hitching when your backgro...
So you are building an IDE extension. Maybe it syncs a collaborative cursor. Maybe it fetches lint results from a cloud backend. You hit the same fork...
You chose Language Server Protocol because the docs said 'write once, run in any editor.' And it worked—for a while. Then came the feature requests: i...