Eslint: How to disable "unexpected console statement" in Node.js?

Question

I'm using eslint with Sublime Text 3 and I am writing gulpfile.js.

/*eslint-env node*/
var gulp = require('gulp');

gulp.task('default', function(){
    console.log('default task');
});

But eslint keeps showing error : "Error: Unexpected console statement. (no-console)"

I found official document here, but I still don't know how to disable it.

/*eslint-env node*/
var gulp = require('gulp');

/*eslint no-console: 2*/
gulp.task('default', function(){
    console.log('default task');
});

doesn't work, either.

My Sublime Text 3 plugins: SublimeLinter and SublimeLinter-contrib-eslint.

Here's my .eslintrc.js file:

module.exports = {
    "rules": {
        "no-console":0,
        "indent": [
            2,
            "tab"
        ],
        "quotes": [
            2,
            "single"
        ],
        "linebreak-style": [
            2,
            "unix"
        ],
        "semi": [
            2,
            "always"
        ]
    },
    "env": {
        "browser": true,
        "node": true
    },
    "extends": "eslint:recommended"
};

markasoftware · Accepted Answer · 2019-12-08 18:57:08Z

598

Create a .eslintrc.js in the directory of your file, and put the following contents in it:

module.exports = {
    rules: {
        'no-console': 'off',
    },
};

edited Dec 8, 2019 at 18:57

answered Dec 11, 2015 at 3:31

markasoftware

12.7k8 gold badges47 silver badges72 bronze badges

Sign up to request clarification or add additional context in comments.

15 Comments

markasoftware Over a year ago

Well, according to the official github page for the eslint plugin (github.com/roadhump/…), putting a .eslintrc file into your project folder should do the trick...to continue debugging it, I'd recommend trying to run eslint from the command line. Simply install node.js if you don't have it installed, then run npm install eslint from a console/command prompt, then navigate to your project folder in a console/command prompt, and run eslint .

AlexWien Over a year ago

it works (for me) when the file is called .eslintrc.json

Chunky Chunk Over a year ago

Alternatively, you can write "rules": {"no-console": "off"} to be less cryptic. "warn" and "error" being the other 2 options.

Colin D Bennett Over a year ago

The ESLint configuration file used to be simply .eslintrc but now that is deprecated and should be named according to the format used, e.g. .eslintrc.js, .eslintrc.yaml, etc.

German Latorre Over a year ago

Does not work in vue-cli 3: see answer stackoverflow.com/a/53333105/150370

|

Nick F · Accepted Answer · 2016-05-25 09:35:34Z

231

You should update eslint config file to fix this permanently. Else you can temporarily enable or disable eslint check for console like below

/* eslint-disable no-console */
console.log(someThing);
/* eslint-enable no-console */

edited May 25, 2016 at 9:35

Nick F

10.2k7 gold badges80 silver badges96 bronze badges

answered Dec 11, 2015 at 3:53

Exception

8,43924 gold badges89 silver badges141 bronze badges

4 Comments

Jean Y.C. Yang Over a year ago

How to config my .eslintrc, please tell me?

Jonathan Brizio Over a year ago

Not is necessary to add both lines. With only put previous of your console.log the following exception is enough: eslint-disable-next-line no-console.

Gael Over a year ago

Thanks @JonathanBrizio that's exactly what I wanted. A quick and dirty solution to debug something. When I'm done, I will remove the console.log line. I don't want to permanently modify the eslint rules.

Serious Angel Over a year ago

Sometimes, such changes require long-lasting development processes relying on it to be restarted to reload the config in memory, including nuxt-ts, scripts/commands like vite dev or npm run watch, or those which may start live development servers with hot module reload (HMR) features.

Samuel RIGAUD · Accepted Answer · 2024-08-24 09:52:35Z

152

For vue-cli 3 open package.json and under section eslintConfig put no-console under rules and restart dev server (npm run serve or yarn serve)

{
  "eslintConfig": {
    "rules": {
      "no-console": "off",
      // more rules ....
    }
  },
  // the rest of your config ...
}

edited Aug 24, 2024 at 9:52

Samuel RIGAUD

1,6981 gold badge19 silver badges28 bronze badges

answered Nov 16, 2018 at 7:15

GiorgosK

8,4392 gold badges32 silver badges29 bronze badges

6 Comments

muenalan Over a year ago

Thanks, as @markasoftware solution does not work if you come here for a cue-cli project.

Michael Cole Over a year ago

package.json isn't the only way to do this. Separate config files are also a standar.

Denis Over a year ago

Thanks! Rules in docs: configuration eslint.org/docs/user-guide/configuring#configuring-rules, rules: eslint.org/docs/rules

MaxRocket Over a year ago

Which package.json file?

GiorgosK Over a year ago

the one in the root folder @MaxRocket

|

binici · Accepted Answer · 2018-10-10 09:09:23Z

67

The following works with ESLint in VSCode if you want to disable the rule for just one line.

To disable the next line:

// eslint-disable-next-line no-console
console.log('hello world');

To disable the current line:

console.log('hello world'); // eslint-disable-line no-console

answered Oct 10, 2018 at 9:09

binici

9458 silver badges10 bronze badges

Comments

Frank Spin · Accepted Answer · 2017-07-20 14:04:18Z

42

A nicer option is to make the display of console.log and debugger statements conditional based on the node environment.

  rules: {
    // allow console and debugger in development
    'no-console': process.env.NODE_ENV === 'production' ? 2 : 0,
    'no-debugger': process.env.NODE_ENV === 'production' ? 2 : 0,
  },

answered Jul 20, 2017 at 14:04

Frank Spin

1,48315 silver badges23 bronze badges

2 Comments

Sanyam Jain Over a year ago

console msgs still print in production environment

user4609276 Over a year ago

how would this work if .eslintrc is in JSON not regular js file?

dipenparmar12 · Accepted Answer · 2020-09-01 09:57:21Z

18

Alternatively instead of turning 'no-console' off, you can allow. In the .eslintrc.js file put

  rules: {
    "no-console": [
     "warn",
     { "allow": ["clear", "info", "error", "dir", "trace", "log"] }
    ]
  }

This will allow you to do console.log and console.clear etc without throwing errors.

edited Sep 1, 2020 at 9:57

dipenparmar12

3,0251 gold badge34 silver badges46 bronze badges

answered Jun 19, 2020 at 2:40

V.Villacis

9551 gold badge8 silver badges22 bronze badges

2 Comments

Scott Baker Over a year ago

Needs to be JSON, not a JavaScript Object

bfontaine Over a year ago

.eslintrc.js is a JS file, so it does not need to be JSON.

Jose M Bel · Accepted Answer · 2016-05-26 14:57:56Z

16

If you install eslint under your local project, you should have a directory /node_modules/eslint/conf/ and under that directory a file eslint.json. You could edit the file and modify "no-console" entry with the value "off" (although 0 value is supported too):

"rules": {
    "no-alert": "off",
    "no-array-constructor": "off",
    "no-bitwise": "off",
    "no-caller": "off",
    "no-case-declarations": "error",
    "no-catch-shadow": "off",
    "no-class-assign": "error",
    "no-cond-assign": "error",
    "no-confusing-arrow": "off",
    "no-console": "off",
    ....

I hope this "configuration" could help you.

answered May 26, 2016 at 14:57

Jose M Bel

1691 silver badge2 bronze badges

2 Comments

user234461 Over a year ago

Even better, just run this handy script on all your files: find . -name '*.js' -exec gawk -i inplace 'NR==1{print "/* eslint-disable */"} {print}' {} \;

Denis Over a year ago

Rules in docs: configuration eslint.org/docs/user-guide/configuring#configuring-rules, rules: eslint.org/docs/rules

Koen · Accepted Answer · 2018-02-14 15:42:08Z

15

If you just want to disable the rule once, you want to look at Exception's answer.

You can improve this by only disabling the rule for one line only:

... on the current line:

console.log(someThing); /* eslint-disable-line no-console */

... or on the next line:

/* eslint-disable-next-line no-console */
console.log(someThing);

answered Feb 14, 2018 at 15:42

Koen

3,6912 gold badges37 silver badges58 bronze badges

Comments

Benjineer · Accepted Answer · 2017-04-09 05:25:21Z

11

I'm using Ember.js which generates a file named .eslintrc.js. Adding "no-console": 0 to the rules object did the job for me. The updated file looks like this:

module.exports = {
  root: true,
  parserOptions: {
    ecmaVersion: 6,
    sourceType: 'module'
  },
  extends: 'eslint:recommended',
  env: {
    browser: true
  },
  rules: {
    "no-console": 0
  }
};

answered Apr 9, 2017 at 5:25

Benjineer

1,68020 silver badges25 bronze badges

Comments

stackdave · Accepted Answer · 2018-11-28 02:17:21Z

10

2018 October,

just do:

// tslint:disable-next-line:no-console

the anothers answer with

// eslint-disable-next-line no-console

does not work !

answered Nov 28, 2018 at 2:17

stackdave

7,1629 gold badges41 silver badges59 bronze badges

Comments

huang botao · Accepted Answer · 2018-12-19 12:02:57Z

10

in my vue project i fixed this problem like this :

vim package.json
...
"rules": {
    "no-console": "off"
},
...

ps : package.json is a configfile in the vue project dir, finally the content shown like this：

{
  "name": "metadata-front",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "serve": "vue-cli-service serve",
    "build": "vue-cli-service build",
    "lint": "vue-cli-service lint"
  },
  "dependencies": {
    "axios": "^0.18.0",
    "vue": "^2.5.17",
    "vue-router": "^3.0.2"
  },
  "devDependencies": {
    "@vue/cli-plugin-babel": "^3.0.4",
    "@vue/cli-plugin-eslint": "^3.0.4",
    "@vue/cli-service": "^3.0.4",
    "babel-eslint": "^10.0.1",
    "eslint": "^5.8.0",
    "eslint-plugin-vue": "^5.0.0-0",
    "vue-template-compiler": "^2.5.17"
  },
  "eslintConfig": {
    "root": true,
    "env": {
      "node": true
    },
    "extends": [
      "plugin:vue/essential",
      "eslint:recommended"
    ],
    "rules": {
        "no-console": "off"
    },
    "parserOptions": {
      "parser": "babel-eslint"
    }
  },
  "postcss": {
    "plugins": {
      "autoprefixer": {}
    }
  },
  "browserslist": [
    "> 1%",
    "last 2 versions",
    "not ie <= 8"
  ]
}

answered Dec 19, 2018 at 12:02

huang botao

5166 silver badges15 bronze badges

1 Comment

swiesend Over a year ago

this is helpful if one generated a vue project trough vue-cli or vue ui and it contains a vue.config.js and package.json. Edit the package.json.

Rob · Accepted Answer · 2019-10-26 05:40:34Z

9

If you're still having trouble even after configuring your package.json according to the documentation (if you've opted to use package.json to track rather than separate config files):

"rules": {
      "no-console": "off"
    },

And it still isn't working for you, don't forget you need to go back to the command line and do npm install again. :)

answered Oct 26, 2019 at 5:40

Rob

2764 silver badges12 bronze badges

1 Comment

Nicke Manarin Over a year ago

Interesting, that what happened to me. Why did we need to run npm install again? Or perhaps I just needed to restart with npm run serve.

Katinka Hesselink · Accepted Answer · 2018-10-31 08:41:54Z

5

In package.json you will find an eslintConfig line. Your 'rules' line can go in there like this:

  "eslintConfig": {
   ...
    "extends": [
      "eslint:recommended"
    ],
    "rules": {
      "no-console": "off"
    },
   ...
  },

answered Oct 31, 2018 at 8:41

Katinka Hesselink

4,2034 gold badges24 silver badges25 bronze badges

Comments

Alessander Franca · Accepted Answer · 2018-10-25 10:54:57Z

4

You should add one rule and add your env:

{
  "rules": {
    "no-console": "off"
  },
  "env": {
    "browser": true
  }
}

you can add other envs.

edited Oct 25, 2018 at 10:54

answered Aug 29, 2018 at 13:22

Alessander Franca

2,8112 gold badges32 silver badges53 bronze badges

Comments

gildniy · Accepted Answer · 2023-06-07 17:53:28Z

4

Alternatively, you can restrict only some methods on the console object with:

"rules": {
    ...
    "no-console": [
      "error",
      {
        "allow": [
          "log",
          "error"
        ]
      }
    ],
    ...
  },

answered Jun 7, 2023 at 17:53

gildniy

3,9731 gold badge38 silver badges25 bronze badges

Comments

Lakshan Hettiarachchi · Accepted Answer · 2020-09-08 08:33:13Z

2

in "rules", "no-console": [false, "log", "error"]

answered Sep 8, 2020 at 8:33

Lakshan Hettiarachchi

4415 silver badges7 bronze badges

Comments

Fabio Ribeiro de Carvalho · Accepted Answer · 2023-03-14 16:24:13Z

1

To just allow `console.error()`

warn the consoles for the debug proposes.

Add other console types in the array if needed.

module.exports = {
// ...
  rules: {
     // ...
    "no-console": ["warn", { "allow": ["error"] }],
  },
// ...
};

answered Mar 14, 2023 at 16:24

Fabio Ribeiro de Carvalho

7989 silver badges25 bronze badges

Comments

Andre Goulart · Accepted Answer · 2020-10-28 14:44:53Z

0

My 2 cents contribution:

Besides removing the console warning (as shown above), it's best to remove yours logs from PROD environments (for security reasons). The best way I found to do so, is by adding this to nuxt.config.js

  build: {
   terser: {
      terserOptions: {
        compress: {
          //this removes console.log from production environment
          drop_console: true
        }
      }
    }
  }

How it works: Nuxt already uses terser as minifier. This config will force terser to ignore/remove all console logs commands during compression.

answered Oct 28, 2020 at 14:44

Andre Goulart

6344 silver badges24 bronze badges

Comments

technik · Accepted Answer · 2023-04-06 09:34:52Z

0

Just a workaround to avoid using the eslint-disable-next-line no-console, or adding rule in .eslintrc, or getting an Eslint warning. You can create a tempotary variable and call it instead.

const cons = console;
cons.log('My message here'); // <- won't see warning here

answered Apr 6, 2023 at 9:34

technik

1,09611 silver badges17 bronze badges

Comments

Samuel Quiroz · Accepted Answer · 2022-01-17 22:44:14Z

-1

make sure that the name of the folder that the flutter project is in. Doesn't have spaces. that was my error

answered Jan 17, 2022 at 22:44

Samuel Quiroz

3713 silver badges6 bronze badges

Comments

Kartik Bhargav · Accepted Answer · 2019-11-09 19:06:22Z

-6

Use Window Object

window.console.log("..")

answered Nov 9, 2019 at 19:06

Kartik Bhargav

3933 silver badges4 bronze badges

1 Comment

DoloMike Over a year ago

This answers the question succinctly and should not be downvoted. In my case, I either have to edit an .env file then rebuild or use a comment // eslint-disable-next-line no-console. Both of which are more tedious than this approach. I can simply use this for quick testing then remove when I'm done. Thank you!

Collectives™ on Stack Overflow

Eslint: How to disable "unexpected console statement" in Node.js?

21 Answers 21

15 Comments

4 Comments

6 Comments

Comments

2 Comments

2 Comments

2 Comments

Comments

Comments

Comments

1 Comment

1 Comment

Comments

Comments

Comments

Comments

To just allow `console.error()`

Comments

Comments

Comments

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

21 Answers 21

15 Comments

4 Comments

6 Comments

Comments

2 Comments

2 Comments

2 Comments

Comments

Comments

Comments

1 Comment

1 Comment

Comments

Comments

Comments

Comments

To just allow console.error()

Comments

Comments

Comments

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related

To just allow `console.error()`