JSHint giving 'Read Only' error for reassignment of $

javascript jshint
Spencer Carnage picture Spencer Carnage · Dec 13, 2011 · Viewed 7.9k times · Source

I'm using the node-jshint command line to lint all of my JS files. I'm doing a reassignment of the $ by:

$ = someWindowObj.document.id;

and its giving me the error "Read Only." I am using Mootools so I am setting the option mootools to true. When I turn the option off in the file itself, via /*jshint mootools:false*/ I'm still getting the error. Shouldn't disabling the mootools (or jquery) option also disable the error? When I remove the mootools option completely from the ~/.jshintrc and the JS file, the error doesn't report.

I'm not sure if this is a bug or the intended behavior so I thought I put it to SO before submitting a bug.

Answer

Anton Kovalyov picture Anton Kovalyov · Dec 14, 2011

If the project settings overwrite in-file settings you should file a bug report for the node-jshint project. In the meantime, you can always do /*global $:true */. This tells JSHint that it is okay to overwrite $ global variable.

Related questions

Turning off eslint rule for a specific line

In order to turn off linting rule for a particular line in JSHint we use the following rule: /* jshint ignore:start*/ $scope.someVar = ConstructorFunction(); /* jshint ignore:end */ I have been trying to locate the equivalent of the above for eslint.

Read More
Why does JSHint throw a warning if I am using const?

This is the error I get when using const: <error line="2" column="1" severity="warning" message="&apos;const&apos; is available in ES6 (use esnext option) or Mozilla JS extensions (use moz)." source="jshint.W104" /> My code …

Read More
Should I use JSLint or JSHint JavaScript validation?

I am currently validating my JavaScript against JSLint and making progress on, it's assisting me to write better JavaScript - in particular in working with the Jquery library. I have now come across JSHint, a fork of JSLint. So I …

Read More