React JSX error : Unclosed regular expression

Question

Recently I was facing an issue coding React app on Visual Studio code. Because of this issue, whenever I wrote JSX inside the render function of the React Component and saved it, it would go messed up (I mean indentation would get messy). See the pic:

This error was also showing error like: 1. Unclosed regular expression

How to solve this?

Humbuggery

Answer 1

If you are using jshint plugin, remove it and install ESLint plugin.

It is a good replacement for jshint in reactJS work.

Harbinger

After that you should restart the computer for cleaning RAM. – Hideaway

Restarting VS Code should be enough. – Harbinger

this solves my problem, i have the jslint install globally, and esLint extension installed in vscode – Harquebusier

Answer 2

I tried several options like creating a .eslintrc file or .jshintrc file.

But it turned out that in my Visual Studio Code IDE, there was third party extensions(eslint/jslint/tslint/beautify/jsformatter etc) that were causing a big mess in my JSX code.

I had to go to the extensions and disable all the extension which could hinder in the natural process of linting and code cleaning of React framework.

(These extensions are really great. But disabling them helped me in solving this issue of mine, no offense to anyone.)

If you are facing the same issue and the issue persists event after adding a .jshintrc with content:

{
    "esversion": 6
}

then consider disabling the third party extensions.

Hope my answer helped.

Humbuggery

I am pretty sure it was only the formatter. Automatic formatters have many problems. And using multiple formatters at once is just not possible. Using multiple linters at once is probably unnecessary. – Ricci

True it is unnecessary. I just had those linters lying out there for no reason, which was causing the issue. – Humbuggery

ya this help me out – Anabantid

This answer led me to disabling JSHint which solved my issue. – Neckerchief

Answer 3

the extension that did it for me was...

jshint

dbaeumer.jshint
Dirk Baeumer

as @abhay-shiro says, disabling a few extensions will usually resolve the issue.

Schluter

Answer 4

I had the same problem, but it was "beautify" extension which was causing the error, I uninstalled it and installed prettier. It fixed the problem.

Unpretentious

Answer 5

I solved this issue by disabling show syntax errors checkbox in visual studio 2015.

Tools -> options - > text editor -> javascript -> intelliSense -> general -> show syntax errors(disable)

Stepdaughter

This is exactly how the Chernobyl disaster happened. You don't overlook warnings, you get rid of or fix the things that caused them. – Griffin