Invalid position given by 'no-multiple-empty-lines'

[lbdremy]

ESLint returned a point that did not exist in the document being edited.
Rule: no-multiple-empty-lines
Requested range: 107:1

Debug information:

{
  "atomVersion": "1.15.0",
  "linterEslintVersion": "8.1.4",
  "linterEslintConfig": {
    "lintHtmlFiles": false,
    "useGlobalEslint": false,
    "showRuleIdInMessage": true,
    "disableWhenNoEslintConfig": true,
    "eslintrcPath": "",
    "globalNodePath": "",
    "advancedLocalNodeModules": "",
    "eslintRulesDir": "",
    "disableEslintIgnore": false,
    "disableFSCache": false,
    "fixOnSave": false,
    "scopes": [
      "source.js",
      "source.jsx",
      "source.js.jsx",
      "source.babel",
      "source.js-semantic"
    ],
    "rulesToSilenceWhileTyping": [],
    "rulesToDisableWhileFixing": []
  },
  "eslintVersion": "2.13.1",
  "hoursSinceRestart": 53.5,
  "platform": "darwin",
  "eslintType": "local project",
  "eslintPath": "/Volumes/Work/front/node_modules/eslint",
  "editorScopes": [
    "source.js.jsx",
    "meta.function-call.with-arguments.js",
    "meta.method-call.with-arguments.js",
    "meta.method-call.with-arguments.js",
    "punctuation.terminator.statement.js"
  ]
}

[not-an-aardvark]

Might be related to eslint/eslint#8401

[Arcanemagus]

@not-an-aardvark Nope, this is a bug in no-multiple-empty-lines that existed from shortly after it was introduced till it was fixed in ESLint v3.5.0.

@lbdremy Please update to a version of ESLint of at least v3.5.0 to get this fixed for you!