RangeError: Maximum call stack size exceeded

[satya1990]

I was trying set up standard for mocha.
$standard --env mocha
I'm getting the following error logs on console.
Error:
standard: Unexpected linter output:
RangeError: Maximum call stack size exceeded
logs:
at Array.values (native)
at findVariable (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:141:42)
at findVariable (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:145:24)
at checkDestructuring (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:299:34)
at checkProperties (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:373:21)
at checkVariable (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:404:13)
at checkDestructuring (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:301:21)
at checkProperties (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:386:21)
at checkVariable (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:404:13)
at checkDestructuring (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:301:21)

[Sullux]

I'm getting the same thing:

RangeError: Maximum call stack size exceeded
    at findVariable (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:141:40)
    at findVariable (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:145:24)
    at checkDestructuring (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:299:34)
    at checkProperties (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:373:21)
    at checkVariable (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:404:13)
    at checkDestructuring (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:301:21)
    at checkProperties (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:373:21)
    at checkVariable (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:404:13)
    at checkDestructuring (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:301:21)
    at checkProperties (/usr/local/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:373:21)

This is only happening on one project. Other projects on the same system seem to lint fine.

[landon9720]

Same thing here. npm install standard --global; standard ... RangeError etc.

[rajat1saxena]

Same here as well

[gingermusketeer]

I was saw this problem on a project I am working on as well with version 10.0.2 of standard on OSX 10.12.5. The error message was

standard: Unexpected linter output:

RangeError: Maximum call stack size exceeded
    at inspect (util.js:168:13)
    at exports.format (util.js:69:24)
    at Console.log (console.js:43:37)
    at findVariable (/project-folder/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:139:13)
    at findVariable (/project-folder/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:147:24)
    at checkDestructuring (/project-folder/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:302:34)
    at checkProperties (/project-folder/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:376:21)
    at checkVariable (/project-folder/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:407:13)
    at checkDestructuring (/project-folder/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:304:21)
    at checkProperties (/project-folder/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:389:21)

After adding some debugging information to node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js so that I could see the file that was being checked I discovered that I had a nested folder with node_modules in it that appeared to be being checked by eslint. The path was something like /project-folder/nested-folder/node_modules/babel-jest/build/index.js.

Not sure if this is the actual problem or if I was just lucky that removing this unneeded folder solved my issue.

[vramana]

I see the same issue on npm repo reproduced via travis https://travis-ci.org/npm/npm/jobs/251196118

[luispabon]

Same here on Linux, npm 5.0.3, standard 10.0.2 and eslint-plugin-node 4.2.2

Happens on both node 7 and 8

[tunnckoCore]

View: #933.

Search before post.

edit: huh, that issue is older, okey.

[tunnckoCore]

@vramana, @luispabon, @gingermusketeer i may help if post some files, or part of the files :)

[vramana]

@tunnckoCore You can reproduce it with npm latest branch. The error triggers on Travis, so you can use Travis if you can't reproduce it on your machine.

[luispabon]

Okay, the empty project was somehow picking a file on the parent folder containing some dodgy code I reckon standard is looping through forever. I've managed to distill it all down to:

let fs = fs || require('fs')

Steps to reproduce:

1. make a folder somewhere
2. make a .js file containing the code above
3. run npm install standard
4. run node_modules/.bin/standard
5. Profit!

It seems specific to the fs component though.

[tunnckoCore]

Now we can close this, @ematipico, @feross :) v4.2.3 is released by @mysticatea! 🎉

[Flet]

Cool, if folks are having issues still, reinstall standard and it should pull the the fix down :)