Screen shot of error message

ESLint: “Parsing error: Unexpected token” in Visual Studio Code

While adding the plumbing for a new JavaScript website project, I knew it needed an ESLint config to keep my code linted and clean. So I installed ESLint the usual way, answered a few questions to customize my install, and I went along my merry way.

Here’s how to fix “Parsing error: Unexpected token” errors from ESLint when working in Visual Studio Code …

EditorConfig logo

ESLint and EditorConfig in VSCode

To kick off 2019, I wanted to start the new year off with cleaner code, with more automation and less effort.  This post should help you and your team kick your new year off with consistently beautiful code, too!

Most importantly, read through to the end to find out how to turn on the “auto-format on save” settings for ESLint, which allows auto-fixing of many problems every time a file is saved!