javascript - what causes *global module: false* in grunt.js - Stack Overflow

admin管理员组

文章数量:1344170

Many grunt.js-script starts with:

/*global module:false*/
module.exports = function(grunt) {

But what the cause of the ment in the first line?

Many grunt.js-script starts with:

/*global module:false*/
module.exports = function(grunt) {

But what the cause of the ment in the first line?

• javascript
• node.js
• gruntjs

Share Improve this question Follow asked Dec 20, 2012 at 13:24 TLindigTLindig 50.2k33 gold badges3030 silver badges3232 bronze badges

Add a ment  | 

1 Answer 1

Sorted by: Reset to default 16

It's a directive for JSLint or JSHint. It tells the JSLint/JSHint parser that the identifier module is defined elsewhere, so it doesn't throw an error telling you that module is undefined. Without it, the parser will encounter the reference to module and think that you're trying to refer to an undefined variable.

From the JSLint docs:

JSLint also recognizes a /*global*/ directive that can indicate to JSLint that variables used in this file were defined in other files. The directive can contain a ma separated list of names.

And the JSHint docs:

In addition to options, you can let JSHint know what global variables it should expect:

    /*global DISQUS:true, jQuery:false */

In the example above, JSHint will allow you to override DISQUS, but plain if you try to override jQuery.

本文标签： javascriptwhat causes *global module false* in gruntjsStack Overflow