RangeError: Maximum call stack size exceeded
See original GitHub issue- ESLint Version: v5.4.0
- Node Version: v11.6.0
- npm Version: v6.5.0-next.0
What parser (default, Babel-ESLint, etc.) are you using? babel-eslint with React Native
Configuration
{
"env": {
"browser": true,
"jest": true
},
"extends": [
"airbnb",
"plugin:prettier/recommended",
"plugin:flowtype/recommended"
],
"parser": "babel-eslint",
"plugins": ["react", "jsx-a11y", "import", "flowtype"],
"globals": {
"window": true
},
"rules": {
"react/jsx-filename-extension": 0,
"react/sort-comp": 0,
"react/destructuring-assignment": 0,
"react/jsx-wrap-multilines": 0,
"react/no-access-state-in-setstate": 0,
"react/jsx-one-expression-per-line": 0,
"import/no-named-as-default": 0,
"linebreak-style": 0,
"jsx-a11y/href-no-hash": 0,
"no-unused-expressions": "off",
"react/forbid-prop-types": 0,
"no-restricted-globals": "off",
"import/prefer-default-export": 0,
"no-console": 0,
"camelcase": 0,
"no-shadow": 0,
"no-plusplus": 0,
"import/no-extraneous-dependencies": 0,
"import/named": 0,
"import/no-unresolved": [2, { "ignore": ["^@"] }],
"import/extensions": [2, { "ignore": ["^@"] }],
"consistent-return": 0,
"no-param-reassign": 0,
"no-nested-ternary": 0,
"prettier/prettier": [
"error",
{
"bracketSpacing": true,
"singleQuote": true,
"trailingComma": "es5",
"jsxBracketSameLine": false,
"parser": "flow",
"useTabs": false,
"tabWidth": 2
}
],
},
"settings": {
"import/resolver": {
"node": {
"extensions": [".js", ".android.js", ".ios.js"]
}
}
}
}
RangeError: Maximum call stack size exceeded
at Function.keys (<anonymous>)
at hashObject (/Users/davidlevai/Desktop/Work/Classy/Projects/BES/bybesapp/node_modules/eslint-module-utils/hash.js:46:10)
at hashify (/Users/davidlevai/Desktop/Work/Classy/Projects/BES/bybesapp/node_modules/eslint-module-utils/hash.js:18:5)
at Object.keys.sort.forEach.key (/Users/davidlevai/Desktop/Work/Classy/Projects/BES/bybesapp/node_modules/eslint-module-utils/hash.js:49:5)
at Array.forEach (<anonymous>)
at hashObject (/Users/davidlevai/Desktop/Work/Classy/Projects/BES/bybesapp/node_modules/eslint-module-utils/hash.js:46:30)
at hashify (/Users/davidlevai/Desktop/Work/Classy/Projects/BES/bybesapp/node_modules/eslint-module-utils/hash.js:18:5)
at Object.keys.sort.forEach.key (/Users/davidlevai/Desktop/Work/Classy/Projects/BES/bybesapp/node_modules/eslint-module-utils/hash.js:49:5)
at Array.forEach (<anonymous>)
at hashObject (/Users/davidlevai/Desktop/Work/Classy/Projects/BES/bybesapp/node_modules/eslint-module-utils/hash.js:46:30)
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
./node_modules/.bin/eslint --cache --fix ./src
What did you expect to happen? Run
What actually happened? Please include the actual, raw output from ESLint.
RangeError: Maximum call stack size exceeded
at Function.keys (<anonymous>)
at hashObject (/Users/davidlevai/Desktop/Work/Classy/Projects/BES/bybesapp/node_modules/eslint-module-utils/hash.js:46:10)
at hashify (/Users/davidlevai/Desktop/Work/Classy/Projects/BES/bybesapp/node_modules/eslint-module-utils/hash.js:18:5)
at Object.keys.sort.forEach.key (/Users/davidlevai/Desktop/Work/Classy/Projects/BES/bybesapp/node_modules/eslint-module-utils/hash.js:49:5)
at Array.forEach (<anonymous>)
at hashObject (/Users/davidlevai/Desktop/Work/Classy/Projects/BES/bybesapp/node_modules/eslint-module-utils/hash.js:46:30)
at hashify (/Users/davidlevai/Desktop/Work/Classy/Projects/BES/bybesapp/node_modules/eslint-module-utils/hash.js:18:5)
at Object.keys.sort.forEach.key (/Users/davidlevai/Desktop/Work/Classy/Projects/BES/bybesapp/node_modules/eslint-module-utils/hash.js:49:5)
at Array.forEach (<anonymous>)
at hashObject (/Users/davidlevai/Desktop/Work/Classy/Projects/BES/bybesapp/node_modules/eslint-module-utils/hash.js:46:30)
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Are you willing to submit a pull request to fix this bug? No. I don’t know what causes the issue.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
javascript - Maximum call stack size exceeded error
It means that somewhere in your code, you are calling a function which in turn calls another function and so forth, until you...
Read more >Uncaught RangeError: Maximum call ... - Net-Informations.Com
This error is almost always means you have a problem with recursion in JavaScript code, as there isn't any other way in JavaScript...
Read more >JavaScript Error: Maximum Call Stack Size Exceeded
If you see the “Maximum Call Stack Size Exceeded” error, there's likely a problem with a recursive function within your JavaScript code.
Read more >RangeError: Maximum call stack size exceeded - Educative.io
The most common source for this error is infinite recursion. You must have a recursive function in your code whose base case is...
Read more >RangeError: Maximum call stack size exceeded in JavaScript
The "RangeError: Maximum call stack size exceeded" error occurs when a function is called so many times that the invocations exceed the call...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@DLevai94 Thanks for checking! My guess is this is an issue with eslint-plugin-import-- it is probably trying to traverse your import/export statements to build a dependency graph, but by exporting from
.
there is probably a cycle. I would recommend opening an issue in the eslint-plugin-import repository.Looks like we know which file is having the issue:
/Users/davidlevai/Desktop/Work/Classy/Projects/BES/bybesapp/src/components/Pager/index.js
Unfortunately, the debug logs and the stack trace aren’t showing the ESLint (or plugin) file that is getting caught in this stack overflow. 🙁
It does look like this is the first file linted. Could you try running ESLint on just this file (which will probably have the same result), and then on a different file in your project? If both fail, then we can assume it’s (probably) not file-specific.