Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RangeError: Maximum call stack size exceeded #933

Closed
animsaj opened this issue Jun 25, 2017 · 9 comments

Comments

@animsaj
Copy link

commented Jun 25, 2017

    at RegExp.test (native)
    at checkProperties (/usr/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:336:31)
    at checkVariable (/usr/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:404:13)
    at checkDestructuring (/usr/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:301:21)
    at checkProperties (/usr/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:373:21)
    at checkVariable (/usr/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:404:13)
    at checkDestructuring (/usr/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:301:21)
    at checkProperties (/usr/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:386:21)
    at checkVariable (/usr/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:404:13)```
@tunnckoCore

This comment has been minimized.

Copy link

commented Jul 16, 2017

Same here. @feross, more precise stack

% 1 > standard index.js test.js utils.js    
standard: Unexpected linter output:

RangeError: Maximum call stack size exceeded
    at findVariable (/home/charlike/.nvm/versions/node/v8.1.4/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:136:22)
    at findVariable (/home/charlike/.nvm/versions/node/v8.1.4/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:145:24)
    at checkDestructuring (/home/charlike/.nvm/versions/node/v8.1.4/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:299:34)
    at checkProperties (/home/charlike/.nvm/versions/node/v8.1.4/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:386:21)
    at checkVariable (/home/charlike/.nvm/versions/node/v8.1.4/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:404:13)
    at checkDestructuring (/home/charlike/.nvm/versions/node/v8.1.4/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:301:21)
    at checkProperties (/home/charlike/.nvm/versions/node/v8.1.4/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:373:21)
    at checkVariable (/home/charlike/.nvm/versions/node/v8.1.4/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:404:13)
    at checkDestructuring (/home/charlike/.nvm/versions/node/v8.1.4/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:301:21)
    at checkProperties (/home/charlike/.nvm/versions/node/v8.1.4/lib/node_modules/standard/node_modules/eslint-plugin-node/lib/rules/no-deprecated-api.js:386:21)

If you think this is a bug in `standard`, open an issue: https://github.com/feross/standard/issues
@tunnckoCore

This comment has been minimized.

Copy link

commented Jul 16, 2017

Just found that problem comes from utils.js I'll look what so bad is happening there ;d

@tunnckoCore

This comment has been minimized.

Copy link

commented Jul 16, 2017

Yep. Seems like lazy-cache made that problem. Probably eslint-plugin-node does something or analyzes the require, so it fails.

@animsaj, so if you use some kind of caching mechanism try to remove it and run Standard again. That was my problem.

@luispabon

This comment has been minimized.

Copy link

commented Jul 18, 2017

I don't have lazy-cache on my project though.

@tunnckoCore

This comment has been minimized.

Copy link

commented Jul 18, 2017

Yea, probably, but probably the problem is some sort like this, any source may help ;] But yea, definitely seems like bug on their side.

@luispabon

This comment has been minimized.

Copy link

commented Jul 18, 2017

No source, this happens without a single file to lint.

@tunnckoCore

This comment has been minimized.

Copy link

commented Jul 18, 2017

Duh.. ;d Clean cache and reinstall? If you use npm@5+ try npm cache verify.

The whole thing is pretty weird. First issue ( #882 ) is published on May 11, last Standard version on April 14, and the plugin on March 28. No changes, no new versions, plus that it is ~ range.

@luispabon

This comment has been minimized.

Copy link

commented Jul 18, 2017

Edit: will post all my comments to #882 which is older and of which this issue is a duplicate of.

@ematipico

This comment has been minimized.

Copy link
Contributor

commented Jul 18, 2017

Will close as duplicate of #882

@ematipico ematipico marked this as a duplicate of #882 Jul 18, 2017

@ematipico ematipico closed this Jul 18, 2017

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
4 participants
You can’t perform that action at this time.