All Downloads are FREE. Search and download functionalities are using the official Maven repository.

rules.jshint.E015.html Maven / Gradle / Ivy

Go to download

Consume reports generated by jshint for code quality. Also consume reports for code duplication (either simian or cpd). Consumes the unit/integration tests reports (generated by Jasmin) coverage report (lcov generated by Istanbul). The information generated by reports are added in Sonar

There is a newer version: 2.1.0
Show newest version

    

When do I get this error?

The "Unclosed regular expression" error is thrown when JSLint or JSHint encounters a regular expression literal with no closing / character. Here's an example:

x
 
1
var regex = /^unclosed$;
2
JSLint found 1 errorVersion 2015-09-23
Line 0:Expected '/' and instead saw ''.

Why do I get this error?

This error is raised to highlight a fatal JavaScript syntax error. Your code will not run unless you fix this issue. The ECMAScript 5 specification lists the following grammar for regular expression literals (ES5 §7.8.5):

RegularExpressionLiteral ::
    / RegularExpressionBody / RegularExpressionFlags

This production makes it clear that regular expression literal bodies must be terminated by a / character. Not doing so will always cause a syntax error. To fix this issue, simply close the regular expression in question:

2
 
1
var regex = /^closed$/;
2
JSLint found no errorsVersion 2015-09-23

In JSHint 1.0.0 and above you have the ability to ignore any warning with a special option syntax. Since this message relates to a fatal syntax error you cannot disable it.





© 2015 - 2025 Weber Informatics LLC | Privacy Policy