Connect with us


The way to Set Up VS Code for React Growth – SitePoint

React builders want a code editor that permits them to write down React code productively. There are millions of free extensions in VS Code’s market that may assist supercharge your growth workflow. On this article, I’ll spotlight a collection of extensions and settings that may drive your React coding productiveness to knowledgeable stage.

A few of the extensions I’ll checklist right here aren’t React particular, however they’ll enhance your effectivity and coding velocity however. In actuality, you’ll solely discover a handful extensions that will likely be actually helpful in your day by day coding schedule.

Implementing the instruments and strategies listed on this article will in all probability prevent hours of growth work — hours that might have been wasted on resolving many small however essential points. They’ll additionally enable you cut back coding errors. The important thing to productiveness is to automate as many duties as you’ll be able to. The next extensions and settings will enable you obtain that purpose.

Language Help

Once you set up VS Code for the primary time, it offers you lots of options out-of-the field with out using any extensions — reminiscent of syntax highlighting for JavaScript and help for TypeScript and JSX code.

Beneath is a snapshot of the Welcome tab. You possibly can at all times discover it underneath the Assist menu.

That is the place it’s essential carry out the preliminary setup. Since our focus is on React, we’ll begin by establishing JavaScript Language Extension, which can present us with extra options important to our coding productiveness workflow.

JavaScript Language Extension

On the Welcome tab, within the Instruments and languages part, click on the JavaScript hyperlink to put in. A reload immediate will seem, which it is best to click on for the brand new function to take impact.

The JavaScript language extension gives a number of options, together with:

  • Intellisense
  • Snippets
  • JSDoc help
  • Hover info
  • Auto imports

The complete checklist and documentation for these options may be discovered within the VS Code docs. I extremely suggest you learn every function to get acquainted on easy methods to use them in your growth workflow.

Pictured under is an instance of Intellisense and Auto import in motion.

autocomplete demo

When the tab key’s pressed, the Header element is imported on the prime. The closing > image needs to be typed in, which can autocomplete the code as: <Header><Header/>.

After putting in the JavaScript language function, VS Code could immediate you to supply a jsconfig.json file on the root of your undertaking. It isn’t vital, however setting this up will assist IntelliSense present extra correct prompts. Right here’s a pattern config:

  "compilerOptions": {
    "module": "commonjs",
    "goal": "es6",
    "baseUrl": ".",
    "paths": {
      "~/*": ["./*"],
      "@/*": ["./src/*"],
      "~~/*": ["./*"],
      "@@/*": ["./*"]
  "exclude": ["node_modules", ".cache", "dist"]

The above configuration tells the JavaScript language server which recordsdata are a part of your supply code and which of them aren’t. This ensures the language service solely analyzes your supply code and subsequently performs quick. The complete configuration has been documented right here, explaining all of the attainable values that can be utilized in jsconfig.js.

TypeScript Help

TypeScript is extremely advisable should you’re wanting into constructing large-scale, advanced React tasks. It is because TypeScript gives sort security and thus reduces the possibilities of delivering buggy code in your front-end purposes. VS Code does present TypeScript language help out of the field by offering a lot of options, reminiscent of:

  • Syntax and Semantic Highlighting
  • IntelliSense
  • Snippets
  • JS Doc help
  • Hover info and Signature Assist
  • Formatting
  • JSX and auto closing tags

The complete checklist is documented right here. With TypeScript, JSX code is written in .tsx file extensions. When compiled, the output will lead to a file with a .jsx extension.

Do observe that VS Code doesn’t present a compiler for TypeScript. You need to set up one in your international Node.js surroundings like this:

npm set up -g typescript

Alternatively, you’ll be able to set up the extension Compile Hero Professional, which gives a compiler for TypeScript and lots of different languages, together with:

  • Much less
  • Sass, SCSS
  • Stylus
  • Jade
  • Pug

The extension gives many extra configurable choices on when and easy methods to compile your TypeScript and styling code. When you’d prefer to be taught extra about establishing React and TypeScript, I’d suggest you take a look at our different article, “React with TypeScript: Greatest Practices”, for a extra detailed rationalization.


Circulate is Fb’s different to TypeScript. It gives the identical options however solely works with React tasks and is much less widespread. VS Code doesn’t help it natively, however you’ll be able to set up the extension Circulate Language Help, which gives a restricted variety of options reminiscent of IntelliSense and Rename.

Keymap Settings

When you’re migrating to VS Code from one other code editor, you’ll be glad to be taught you’ll be able to proceed utilizing the identical keyboard shortcuts that you simply had been already used to. When you’re new to code editors, do skip this part. Nevertheless, should you’ve used code editors earlier than, you’re in all probability conscious that re-training your muscle reminiscence is unproductive and it takes time to regulate.

On the Welcome tab, underneath the Settings and key bindings part, you’ll see hyperlinks for putting in keyboard shortcuts for Vim, Elegant, Atom and others. When you click on the others hyperlink, you’ll get a full checklist of keymaps you’ll be able to set up.

vscode keymaps

I was an Atom consumer earlier than I switched to VS Code. Establishing Atom’s keymap in VS Code is so simple as clicking the Atom hyperlink. This can set up the Atom Keymap extension for me. The next configuration in settings.json is required to make VS Code extra “Atom like”:

"atomKeymap.promptV3Features": true,

"editor.multiCursorModifier": "ctrlCmd",

"window.openFoldersInNewWindow": "on",

Do learn the directions supplied by your keyboard shortcut extension on easy methods to set yours up. The documentation may be discovered by merely clicking on the keymap extension within the Extension Bar.

Emmet JSX Help

Emmet is an internet growth toolkit that permits you write HTML code extra effectively. When you’re new to Emmet, take a look at the demo to see the way it works.

VS Code comes with Emmet inbuilt, and it already helps JSX syntax. Sadly, most React starter tasks use the .js extension. The difficulty with that is that VS Code doesn’t acknowledge such recordsdata as React code, so JSX options aren’t activated. There are two methods of fixing this:

  1. Rename all of your recordsdata with JSX code to .jsx extension (advisable)

  2. Configure VS Code to acknowledge all .js recordsdata as React recordsdata. Replace your settings.json as follows:

    "emmet.includeLanguages": {
      "javascript": "javascriptreact"

To entry settings.json, merely go to the highest menu tab then click on View > Command Palette. Sort “settings” after which select the choice Preferences: Open Settings(JSON). Alternatively, you’ll be able to press Ctrl + P then sort “settings.json” to open the file rapidly. You may also use the shortcut Ctrl + , to open the UI model of Settings in a brand new tab. The primary prime right-hand nook icon button will open settings.json if you click on on it.

The second possibility appears to be the simplest route. Sadly, this causes points with different JavaScript growth instruments reminiscent of eslint-config-airbnb, which has a ruleset that enforces the .jsx file extension for React code. Disabling that rule will trigger different points in a while.

The official React crew do suggest utilizing .js extension for React code. From my private expertise, it’s higher to rename all recordsdata with React code to .jsx , and use a .js extension for recordsdata containing plain JavaScript code. This fashion, you’ll have a neater workflow with all growth instruments.


Writing high-quality code requires you to write down constant code. As builders, we’re human, and it’s very simple to overlook the requirements we’ve set for ourselves. On this part, we’ll have a look at the important instruments that may assist us automate the writing of constant code.


EditorConfig is a straightforward configuration file that comprises solely formatting guidelines. You’ll have to put in an extension that may permit VS Code to learn these guidelines and override its personal. Merely undergo the next steps to set it up:

  1. Set up the EditorConfig for VS Code extension. Do observe this can override consumer/workspace settings with settings present in .editorconfig recordsdata.

  2. Create a .editorconfig file on the root of your undertaking and replica this instance config:

    root = true
    indent_style = house
    indent_size = 2
    end_of_line = lf
    charset = utf-8
    trim_trailing_whitespace = true
    insert_final_newline = true

VS Code will now observe these guidelines to format your code. Let’s rapidly speak about line endings. Home windows makes use of CRLF to point termination of a line, whereas UNIX-based methods use LF. When you occur to make use of recordsdata with blended line endings, you’ll encounter a lot of points when committing recordsdata. You possibly can configure Git on easy methods to deal with line endings.

The strategy I favor is simply to implement all undertaking recordsdata on any platform to make use of the LF line endings. Do observe that EditorConfig gained’t convert line endings for current recordsdata. It should solely set the LF for brand new recordsdata. To transform all current recordsdata, you have got two selections:

  • do it manually (click on the textual content CRLF on the standing bar to modify)
  • use prettier to format all of your recordsdata

Let’s have a look at Prettier subsequent.


Prettier is the simplest code formatter to arrange for JavaScript code. It helps JavaScript, TypeScript, JSX, CSS, SCSS, Much less and GraphQL. To set it up, undergo the next steps:

  1. Set up the Prettier code formatter extension.

  2. Guarantee VS Code makes use of Prettier as its default formatter. Replace settings.json as follows:

       "editor.defaultFormatter": "esbenp.prettier-vscode", 
       "editor.formatOnPaste": true, 
       "editor.formatOnType": true, 
       "editor.formatOnSave": true, 
       "recordsdata.trimTrailingWhitespace": true, 
       "recordsdata.trimFinalNewlines": true, 
  3. Set up Prettier as a dev dependency in your undertaking: npm set up --save-dev prettier or yarn add -D prettier.

  4. Create .prettierrc and replica the next instance guidelines:

         "arrowParens": "keep away from", 
         "semi": false 
  5. Replace package deal.json by including this command to your scripts part:

      "scripts": {
        "format": "prettier --ignore-path .gitignore --write ."

For the steps 3–5, you’ll should do it for every undertaking that you really want Prettier to help. Now you can click on the format command underneath the npm scripts panel on VS Code, proven within the screenshot under.

run npm scripts

Alternatively, you’ll be able to simply run the command npm run format to run Prettier.

This can trigger all of your recordsdata to be reformatted correctly and persistently in accordance with Prettier’s default guidelines and people that you’ve overridden in .prettierrc and .editorconfig recordsdata. Line endings may also be made constant too.

As you could have seen, code format settings are actually positioned in three completely different areas. You might surprise what’s going to occur if we’ve conflicting guidelines. With Prettier activated, it should deal with these guidelines in accordance with the next precedence:

  1. Prettier configuration file
  2. .editorconfig
  3. VS Code Settings (ignored if another configuration is current)

Prettier configuration takes priority in case there’s any battle.


As any true developer value their salt is aware of, it’s widespread to repeat HTML code you discovered someplace from the Web and paste it into your React code. This typically requires that you simply convert HTML attributes into legitimate JSX syntax. Fortuitously, there’s an extension known as html to JSX that may carry out the conversion for you. As soon as you put in it, it should mean you can simply:

  • convert current HTML code into JSX
  • convert HTML code into legitimate JSX syntax whereas pasting

This implies attributes reminiscent of class will likely be transformed to className. It is a actually nice timesaver.

React Snippets

On VS Code’s market, there are fairly a lot of snippet extensions for JavaScript tasks. For React, the preferred one is ES7 React/Redux/GraphQL/React-Native snippets. As soon as you put in this one, you in all probability gained’t want to put in one other, because it comes with greater than sufficient snippets than you’ll be able to memorize.

Right here’s a pattern of JavaScript snippets:

Prefix Technique
imp→ import moduleName from 'module'
imn→ import 'module'
imd→ import { destructuredModule } from 'module'
exp→ export default moduleName
exd→ export { destructuredModule } from 'module'
edf→ export default (params) => { }
nfn→ const functionName = (params) => { }
dob→ const {propName} = objectToDescruct

The extension gives many extra snippets which are particular to:

  • React
  • React Native
  • Redux
  • GraphQL
  • PropTypes
  • Console
  • Check Scripts

There are additionally snippets that insert full React parts. For instance, typing “rfc” then urgent tab will insert the next React element snippet for you:

import React from 'react'

export default operate $1() {
  return <div>$0</div>

When you’re going to put in this extension, you higher memorize a minimum of a handful of the snippets that will help you write code sooner. Utilizing snippets is quicker than copy–pasting.


Writing React code typically requires you to write down easy and quick statements so as to check performance early. Very often, you’ll discover the necessity to reuse the code you wrote. This implies it’s essential extract and refactor your code so as to fulfill the “write as soon as, use in every single place” mantra.

You possibly can take the time to refactor your code manually, or you’ll be able to velocity the method up through the use of VS Code React Refactor that will help you refactor your code in simply two steps.

react refactor demo

Fairly neat, proper?

On this part, we’ll have a look at extensions that enable you automate frequent code operations as you sort.

Auto Shut Tag

Whereas not utilizing Emmet, the Auto Shut Tag extension can assist you shut JSX tags mechanically. It additionally locations the cursor between tags as quickly because it closes.

Right here’s a fast demo of the extension in motion:

auto close tag gif

Auto Rename Tag

As you write JSX code, you’ll typically end up renaming tags, reminiscent of <div> to <part>. Once you carry out these modifications, the closing tag stays unchanged. Altering it manually is bothersome, particularly if it’s a standard incidence. You possibly can automate renaming tags with by putting in the Auto Rename Tag extension. As soon as put in, it should mechanically rename your closing tag in actual time as you edit the opening tag.

auto rename demo


Linting in React is an important a part of a TDD toolchain that helps you ship high-quality code. It’s additionally a vital step when the codebase is being shared throughout a crew of builders, because it enforces a constant coding fashion for all. Linting is extraordinarily helpful for catching errors as you sort new code.

ESLint is the preferred JavaScript linter and is the simplest to configure and arrange. ESLint has a quantity plugins that help the React library. Help for ESLint in VS Code is supplied by the ESLint extension. When lively, VS Code will repeatedly run ESLint within the background and spotlight errors for you as you sort and save your code. The extension additionally gives an choice to auto-fix points by way of the context menu.

Much like Prettier, there are a variety of steps which are required to be adopted for the ESLint extension to work. Establishing ESLint in VS Code to work together with your undertaking is a little bit of a course of, and I’d suggest you take a look at this video on easy methods to set up and configure ESLint.

Do take a look at our article “Up and Operating with ESLint” if you need extra info on JavaScript linting. You ought to be conscious that there’s an eslint-plugin-prettier plugin that’s required to be put in to make sure each Prettier and ESLint play effectively collectively.

There are different linter instruments accessible, however you’ll seemingly conclude that ESLint is the very best.


As we come to the top of this text, I’d like to say that there are various extra JavaScript VS Code extensions that you could be be enthusiastic about. One extension I’d like to spotlight is Bracket Pair Colorizer 2. I’ve discovered it very helpful in figuring out lengthy sections of code blocks. The extension provides each pair of matching brackets a special colour, making it simple to see the place one code block ends and one other begins.

We’re additionally residing within the age of AI, and it will be prudent for me to say concerning the new AI-assisted growth extensions that are actually accessible in VS Code’s market. I don’t have a lot expertise with them but, however I believed I’d checklist essentially the most distinguished ones right here:

From my analysis, Tabnine appears to be getting essentially the most love from JavaScript builders. It does an excellent job of predicting your subsequent line of code by offering higher strategies than IntelliSense. Right here’s an fascinating dialog I got here throughout concerning the extension:

I hope this information will enable you enhance your coding velocity and productiveness immensely as you develop your React tasks utilizing VS Code.

Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *