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 #1254

Closed
jfoclpf opened this issue Feb 23, 2019 · 1 comment

Comments

@jfoclpf
Copy link

commented Feb 23, 2019

What version of standard?

12.0.1

What operating system, Node.js, and npm version?

node v 9.4.0
npm v 6.8.0

What did you expect to happen?

no error, just to check all the js files in the module

What actually happened?

standard: Unexpected linter output:

RangeError: Maximum call stack size exceeded
    at RegExp.[Symbol.match] (<anonymous>)
    at String.match (native)
    at Literal (/home/jfolpf/autocosts/node_modules/standard/node_modules/eslint/lib/rules/no-octal-escape.js:33:40)
    at listeners.(anonymous function).forEach.listener (/home/jfolpf/autocosts/node_modules/standard/node_modules/eslint/lib/util/safe-emitter.js:45:58)
    at Array.forEach (<anonymous>)
    at Object.emit (/home/jfolpf/autocosts/node_modules/standard/node_modules/eslint/lib/util/safe-emitter.js:45:38)
    at NodeEventGenerator.applySelector (/home/jfolpf/autocosts/node_modules/standard/node_modules/eslint/lib/util/node-event-generator.js:251:26)
    at NodeEventGenerator.applySelectors (/home/jfolpf/autocosts/node_modules/standard/node_modules/eslint/lib/util/node-event-generator.js:280:22)
    at NodeEventGenerator.enterNode (/home/jfolpf/autocosts/node_modules/standard/node_modules/eslint/lib/util/node-event-generator.js:294:14)
    at CodePathAnalyzer.enterNode (/home/jfolpf/autocosts/node_modules/standard/node_modules/eslint/lib/code-path-analysis/code-path-analyzer.js:632:23)

I already checked issue #882 and #993 with no help. I don't have module utils.js installed.

Just a further tip: this error message should be more precise on which file the problem resides.

@stale

This comment has been minimized.

Copy link

commented May 24, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label May 24, 2019

@stale stale bot closed this May 31, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
You can’t perform that action at this time.