Two Real VS Code Extensions, Built with vsceasy (and What Each Feature Does)
That 90-second video isn't a mockup. Every VS Code frame in it is a real screen recording: two extensions I built with vsceasy , running in VS Code, doing real work. Real keystrokes, real tests, a real local LLM answering. This post walks through what you see in the video and which part of the framework makes each piece possible. What vsceasy is, in one paragraph vsceasy is a CLI and a small…
Two real VS Code extensions demonstrated in a 90-second video were built using the vsceasy framework. This framework provides a CLI and a small framework for building VS Code extensions. The scaffolded project includes a React webview, a typed RPC bridge, file-based routing for panels, commands, menus, and tree views, a mini-ORM, an LLM client, editor-surface helpers, and a language project type for grammar-based extensions.
One file typically corresponds to one feature in the generated extension. The scaffold generates a project structure where you can drop files into folders like panels/, commands/, menus/, or treeViews/ and the generator registers them and updates the contributes section of package.json. There's a typed RPC mechanism where you declare an interface for the RPC contract, implement it on the extension side, and call it from React with fully typed data.
In the Code Trainer extension, each vsceasy feature is showcased in order: sidebar tree views, the problem catalogue, React webviews, commands and quick picks, editor surface, real tests in a real terminal, local LLM + mini-ORM, and a chat panel. For the TOML language extension, the framework generates a TextMate grammar, language configuration, snippets, and a file icon, without requiring React or RPC.
This results in grammar highlighting, language-specific file icons, scoped token colors, and optimized snippet functionality.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.