I released my own Visual Studio Code Extension Pack and here is how you can too

by lampe3 on 8/11/2019, 1:32 PM with 18 comments
  • by Kipters on 8/11/2019, 3:22 PM

    You can add an "extensions.json" file inside of your workspace's .vscode directory with a list of recommended extensions[0]. The first time a new coworker joins the team, he only needs to pull the project and open it in VSCode, the editor will notice the file and prompt you to install the recommended extensions. The same thing can be done in the devcontainer.json file[1].

    If you put the remote development extension in the "local" recommended, and the required extensions in the "remote" recommended, the requirements for the onboarding of a new team member boil down to "install VSCode, Docker and docker-compose"

    [0] https://code.visualstudio.com/docs/editor/extension-gallery#...

    [1] https://code.visualstudio.com/docs/remote/remote-overview

  • by qntmfred on 8/11/2019, 2:58 PM

    > People forget what extensions they have installed

    automatically sync your settings into a Gist with https://marketplace.visualstudio.com/items?itemName=Shan.cod...

    bonus - if you work on multiple machines, it'll automatically update from one machine to the next too

  • by gravypod on 8/11/2019, 5:25 PM

    One day I hope someone builds a VS Code distribution that comes as a 1-step setup as an IDE for "all" languages. So long as you have docker (or snap or whatever is favorable then) you can install a plugin and get LSPs, linters, code building, etc setup for "all" languages. Also autocomplete for things like proto/thrift files would be cool (by finding .proto and .thift files, running code gen, and indexing that in the language server).

    One can dream...

  • by finchisko on 8/11/2019, 2:32 PM

    Bit offtopic. But I'm looking for extensios, that will allow me to set pernament filter on directories that are displayed in the explorer (sidebar). I quite often need to check some source file from node_modules and scrolling through all installed modules is painful. I wish I could filter those directories, like you can do in search (files to include/exclude).

  • by dmortin on 8/11/2019, 3:09 PM

    Compared to Emacs extensions where you simply eval your new function and it becomes part of the editor this process is quite complicated.

    Those who don't know Emacs can't really understand how quick it is to write extensions for emacs.

    I wonder why VSCode could not replicate this simplicity instead of creating package.json files and stuff.