Skip to content
This repository has been archived by the owner on Aug 18, 2021. It is now read-only.

complex template string cause 'Maximum call stack size exceeded' error #636

Closed
clark-t opened this issue Jun 21, 2018 · 2 comments
Closed

Comments

@clark-t
Copy link

clark-t commented Jun 21, 2018

env

node: 8.11.1
eslint: 4.19.1
babel-eslint: 8.2.3

description

the code is:

console.log(`it is ${
  'complex'.split('').map(str => {
    return `${str}`
  }).join('')
}`)

and causes this error:

Maximum call stack size exceeded
RangeError: Maximum call stack size exceeded
    at RegExp.test (<anonymous>)
    at OffsetStorage.getDesiredIndent (/Users/test/node_modules/eslint/lib/rules/indent.js:445:32)
    at OffsetStorage.getDesiredIndent (/Users/test/node_modules/eslint/lib/rules/indent.js:451:45)
    at OffsetStorage.getDesiredIndent (/Users/test/node_modules/eslint/lib/rules/indent.js:451:45)
    at OffsetStorage.getDesiredIndent (/Users/test/node_modules/eslint/lib/rules/indent.js:451:45)
    at OffsetStorage.getDesiredIndent (/Users/test/node_modules/eslint/lib/rules/indent.js:451:45)
    at OffsetStorage.getDesiredIndent (/Users/test/node_modules/eslint/lib/rules/indent.js:451:45)
    at OffsetStorage.getDesiredIndent (/Users/test/node_modules/eslint/lib/rules/indent.js:451:45)
    at OffsetStorage.getDesiredIndent (/Users/test/node_modules/eslint/lib/rules/indent.js:451:45)
    at OffsetStorage.getDesiredIndent (/Users/test/node_modules/eslint/lib/rules/indent.js:451:45)

my .eslintrc is:

{
  "parser": "babel-eslint",
  "rules": {
      "indent": ["error", 2]
  }
}

when remove babel-eslint and change eslintrc to:

{
  "parserOptions": {
    "ecmaVersion": 8
  },
  "rules": {
      "indent": ["error", 2]
  }
}

eslint runs well, so I think this bug should be caused by babel-eslint

@existentialism
Copy link
Member

@clark-t thanks for the issue! This looks like a duplicate of #603, which was fixed by #610. We’ll cut a new release ASAP!

@existentialism
Copy link
Member

@clark-t just published 8.2.4, which should fix the issue!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants