⚠ Outdated: now VSCode support profiles

VSCode without a doubt it's an amazing tool, but for me, is missing an important setting to enable/disable extensions depending on language or workspace.

Almost me, jump all day between projects in different languages and I have a lot of extensions and settings that are useless in each scenario consuming resources. You can disable it manually on each project, but if you create a new one, you gonna need to make it all again. That's a waste of time.

While the VSCode team solves that, we can use a little workaround, creating our dedicated profile for Node development.

It's not perfect, because you can share those extensions that you use in multiples scenarios. But I prefer missing a little space on the disk in favor of fast settings configurations.

Create Profile

We are going to create a new profile folder for extensions and data using --extensions-dir and --user-data-dir parameters.

⚠️ WSL2 does not support --extensions-dir or --user-data-dir flags

How to use?

Are you crazy? We need to write and memorize this long command each time we want to work with Node?.

No, of course not.

On macOS/Linux

On this path $HOME/.vscode/profiles/node/ download this image:

Dock Launcher

On same path, create a file called code-node.command with this code inside:

open -n -a "Visual Studio Code.app" --args --extensions-dir="$HOME/.vscode/profiles/node/extensions" --user-data-dir="$HOME/.vscode/profiles/node/data"

Save it and execute permission with chmod +x code-node.command.

Copy the icon-node.png content on the Clipboard. One way to do this is to open the picture in Preview, choose Edit > Select All, then choose Edit > Copy or press Command-C.

Select code-node.command file, then choose File > Get Info. At the top of the Info window, click the picture of the icon to select it, then choose Edit > Paste or press Command-V.

Select code-node.command file, then choose File > Make Alias or press Command-L name it as VSCode Node (with blank space between). Just drag and drop this alias shortcut to your Dock or Desktop.

Recommended configurations: Open a terminal window, go to 'Preference > Profiles. Set Auto close terminal on exit: inside 'Shell' tab, select "Close if the shell exited cleanly" on "When the shell exits" option.

Alias

An alias can be our best friend in those cases. Open your .zshrc or .bash_profile and paste this.

alias code-node="code --extensions-dir \"$HOME/.vscode/profiles/node/extensions\" --user-data-dir \"$HOME/.vscode/profiles/node/data\""

Save your file and restart your terminal window. Now you can open a folder project in VSCode with code . command, but now, if you going to work with Node use code-node . instead.

On Windows

On this path %HOMEPATH%/.vscode/profiles/node/extensions download this icon:

Shortcut

On the same path, create a shortcut file and set with these properties:

Named as: VSCode Node

Set target as:

"C:\Users\%USERNAME%\AppData\Local\Programs\Microsoft VS Code\Code.exe" --extensions-dir "%HOMEPATH%/.vscode/profiles/node/extensions" --user-data-dir "%HOMEPATH%/.vscode/profiles/node/data"

Start In as :

"C:\Users\%USERNAME%\AppData\Local\Programs\Microsoft VS Code"

And use the icon downloaded previously.

Sadly on Windows create an alias it slightly more complicated than macOS/Linux, then you only can open it using the shortcut and can't open it directly from the project path. But if you are using WSL you can use the same alias approach from mac/linux.

Colors

It will be good to recognize when are using your VSCode and your Node flavored VSCode version.

{
    "workbench.colorCustomizations": {
        "activityBar.background": "#68A063",
        "activityBar.foreground": "#000000",
        "activityBar.inactiveForeground": "#00000099",
        "activityBarBadge.background": "#303030",
        "activityBarBadge.foreground": "#ffffff",
        "statusBar.noFolderBackground": "#3C873A",
        "statusBar.background": "#68A063",
        "statusBar.foreground": "#000000",
        "statusBarItem.hoverBackground": "#3C873A"
    }
}

That's all. Now it's up to you what settings and extensions do you want to install. Those are my favorite recommendations.

Extensions

Editor

• DotENV

• Template String Converter

{
    "template-string-converter.autoRemoveTemplateString": true,
}

• es6-string-html

Debugging

• Debug Visualizer

• Turbo Console Log

{
    "turboConsoleLog.logMessagePrefix": "DEBUG -> "
}

Editor

• es6-string-html

Packages

• Import Cost

• npm Intellisense

• Path Intellisense

{
    "path-intellisense.extensionOnImport": true,
    "javascript.suggest.paths": false,
    "typescript.suggest.paths": false
}

Containers

• Docker

REST

• REST Client

• Thunder Client

• Paste JSON as Code

• vscode-random

Snippets

• dein Snippets Pack - Debug + Const & Props + Arrow Functions

• JavaScript (ES6) code snippets

• node-snippets

Testing

• Test Explorer UI

{
    "testExplorer.errorDecoration": true,
    "testExplorer.errorDecorationHover": true,
    "testExplorer.useNativeTesting": true
}

• Vitest - Test Explorer

• Vitest Snippets

• Code Coverage Highlighter

And remember add coverage folder to .gitignore file.

Sync

I'm not a big fan of the built-in VSCode Sync option because you can use more than one GitHub user account and also you can't create profiles.

But don't worry, we can use the well known Setting Sync extension.

Please create another GitHub account, adding -node to your username and +node to your Gmail account.

With this trick, you can have another GitHub account without creating a new email account. Just use your new username-node account and voilà, your Node flavored VSCode version can be sync across multiple devices.

That’s All Folks!
Happy Coding 🖖