Visual Studio Code
code.visualstudio.com βΊ api βΊ get-started βΊ your-first-extension
Your First Extension | Visual Studio Code Extension API
November 3, 2021 - You can find the source code of this tutorial at: https://github.com/microsoft/vscode-extension-samples/tree/main/helloworld-sample. The Extension Guides topic contains other samples, each illustrating a different VS Code API or Contribution Point, and following the recommendations in our UX Guidelines. In this guide, we mainly describe how to develop VS Code extension with TypeScript because we believe TypeScript offers the best experience for developing VS Code extensions.
Best Vs code extensions you use?
Easy-LESS, and CSS Variable Autocomplete The last one is a big-time saver. More on reddit.com
What is your favourite vs code extension?
Live Share. It just works, itβs fast, and it even lets you share the terminal. More on reddit.com
What VS Code extensions do you actually enjoy/use
Peacock. You can use it to change a color of vscode based on a project. Useful if you are working with multiple projects at the same time. More on reddit.com
Top VS Code Extensions That Make Your Life Easier as a Programmer
Ok fine, but here are some way better ones Excalidraw Git Graph Thunder Client (rest client) ToDo Tree Headwind (tailwind class sorter) And of course Gruvbox Theme More on reddit.com
Videos
32:48
Creating a Visual Studio Code Extension - YouTube
23:24
Full Tutorial | Build A VSCode Extension - YouTube
24:51
How To Create And Deploy A VSCode Extension - YouTube
52:36
Build a Useful VS Code Extension in 50 Minutes (Step-by-Step) - ...
35:56
Top 10 VS Code Extensions for Web Developers (And How to Use Them!)
20 Essential VS Code Extensions
GitHub
github.com βΊ microsoft βΊ vscode-extension-samples
GitHub - microsoft/vscode-extension-samples: Sample code illustrating the VS Code extension API. Β· GitHub
You can read, play with or adapt from these samples to create your own extensions. ... You need to have node and npm installed on your system to run the examples. It is recommended to use the node version used for VS Code development itself which is documented here Β· git clone https://github.com/Microsoft/vscode-extension-samples
Starred by 10K users
Forked by 3.9K users
Languages Β TypeScript 79.1% | JavaScript 15.1% | Rust 3.4% | CSS 1.4% | Jupyter Notebook 0.8% | HTML 0.2%
Snyk
snyk.io βΊ blog βΊ modern-vs-code-extension-development-tutorial
Modern VS Code extension development tutorial: Building a secure extension | Snyk
October 2, 2023 - In our first modern VS Code extension development blog post, we covered the basics of VS Code development, including the architecture and the various types you can create. This article will help you apply that knowledge by showing you how to create and code your very own VS Code extension.
Visual Studio Code
code.visualstudio.com βΊ api βΊ working-with-extensions βΊ publishing-extension
Publishing Extensions | Visual Studio Code Extension API
November 3, 2021 - You can use the engines.vscode property to ensure the extension only gets installed for clients that contain the API you depend on. This mechanism plays well both with Stable and Insiders releases. For example, imagine that the latest Stable version of VS Code is 1.8.0. During the development of ...
GitHub
microsoft.github.io βΊ vscode-essentials βΊ en βΊ 10-create-an-extension.html
Create Your First Extension Β· Visual Studio Code - The Essentials
If you feel a feature is missing, ... your own extension and publish it on the marketplace for everyone to benefit. VS Code itself is written in TypeScript, and uses the Electron framework which is based on Node.js and Chromium. Thus, you need Node.js to develop your ...
Opensource.com
opensource.com βΊ article βΊ 20 βΊ 6 βΊ vs-code-extension
How to write a VS Code extension | Opensource.com
{ "name": "initdockerapp", "displayName": "initdockerapp", "description": "", "version": "0.0.1", "engines": { "vscode": "^1.44.0" }, "categories": [ "Other" ], "activationEvents": [ "onCommand:initdockerapp.initialize" ], "main": "./out/extension.js", "contributes": { "commands": [ { "command": "initdockerapp.initialize", "title": "Initialize A Docker Application" } ] }, "scripts": { "vscode:prepublish": "npm run compile", "compile": "tsc -p ./", "lint": "eslint src --ext ts", "watch": "tsc -watch -p ./", "pretest": "npm run compile && npm run lint", "test": "node ./out/test/runTest.js" }, "d
LogRocket
blog.logrocket.com βΊ home βΊ writing vs code extensions in javascript
Writing VS Code extensions in JavaScript - LogRocket Blog
June 4, 2024 - You can click the Add Configuration button to give you autocompletion assistance, select VS Code Extension Development as the option, and it will fill in the properties. Run the Hello World command from the Command Palette (Ctrl+Shift+P) and you will see a pop-up message saying βHello World!β. Well done, you have written your first VS Code extension! If you used the Yeoman Generator to create a project for you, it will create the folder structure as outlined below. I describe the function of each file: . βββ .vscode β βββ launch.json // Config for launching and debugging the extension.
Brandonscott
brandonscott.me βΊ posts βΊ writing-and-publishing-your-first-visual-studio-code-extension
Writing and Publishing Your First Visual Studio Code Extension
βββ src # Source folder for the extension's TypeScript files β βββ test # Generated extension test suite β βββ extension.ts # Entrypoint for the extension, defines activate/deactivate functions βββ .vscodeignore # Configuration file to exclude files/directories from the packaged extension βββ package.json # Package manifest file defining its name, author, dependencies, as well as extension-specific configurations: commands, activation events, and settings. While most (if not all) of your extension's business logic can live in extension.ts, you are free to break out functions, variables, etc.