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

rules.jshint.E042.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 "Stopping. ({a}% scanned)" error is thrown when JSLint or JSHint encounters a JavaScript syntax error and cannot continue to reliably parse the program. JSHint will only raise this error if the passfail option is set to true. In the following example we have half a variable statement which is invalid and cannot be parsed as a complete JavaScript program:

x
 
1
/*jshint passfail: true */
2
var
3
JSLint found 1 errorVersion 2015-09-23
Line 3:Expected an identifier and instead saw '(end)'.

Why do I get this error?

This error is raised to highlight a fatal JavaScript syntax error and the fact that the parser cannot reliably finish parsing your program. Your code will not run unless you fix this error. The exact cause will depend on your program, but other errors are usually raised along side this one that should guide you to the problem with your code. In our example, the variable statement is missing an identifier:

3
 
1
/*jshint passfail: true */
2
var a;
3
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