Visual Studio Code (VSCode) has rapidly become the favored editor/IDE for a huge swath of web developers. This is in no small part due to its robust extensions marketplace and the fact that you can change how pretty much every little aspect works.
- ESLint is basically required. You’ll still have to install ESLint locally (
npm i eslint) or globally (
npm i -g eslint) via npm.
- npm for validating your
package.jsonfile. It'll show you any obvious errors in VSCode when you have your
- npm intellisense for autocompleting import/require statements.
- Path Intellisense for autocompleting things that look like paths, making it much easier to correctly type out file/folder paths.
- Better Comments for comment highlighting based on keywords.
- Beautify for cleaning up janky-looking files of various types. Use with
beauand choose the option you want.
Ctrl+Shift+Pand then starting typing the case name you want to convert to.
- Prettify JSON to make JSON readable. Use with
Code environment settings can be very personal, or can be dictated from above for matching across a team. In any event, here are the ones I’ve settled on over time (to edit yours in VSCode,
Preferences: Open Settings (JSON) ):
"editor.fontFamily": "'Fira Code', Consolas, 'Courier New', monospace",
"terminal.integrated.shell.windows": "C:\\Program Files\\Git\\bin\\bash.exe",
If you want to use the Fira Code font, you’ll need to first install it.
terminal... fields are for setting Git Bash as the default terminal, if that's the sort of thing you're into.