Introduction In this post, we’re going to cover the file structure of the extension, diving into what individual files are for and discuss the fundamental configuration of them. We’re also going to give an overview of the Extension Manifest (package.json), which is what VS Code will use to determine how and when users will interact with your plugin. Finally, we’ll introduce Contribution Points and Activation Events, two important pieces of the Command Pipeline (my terminology for the flow of functionality in VS Code extensions).
Introduction This is the first of a multi-part series on writing a VS Code extension! If you don’t want to write a VS Code extension, that’s ok! We’ll cover other material that is generally applicable to software engineering projects. Feel free to skim. I will be talking about AWS in this series, but no background knowledge is required. This is strictly a series on building a VS Code extension.