Skip to content
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.

Error: Failed getting range #60

Closed
awcross opened this issue Dec 22, 2016 · 10 comments
Closed

Error: Failed getting range #60

awcross opened this issue Dec 22, 2016 · 10 comments

Comments

@awcross
Copy link

awcross commented Dec 22, 2016

Any time I have multiple empty lines I am getting this error (one popup for each empty line).

Error: Failed getting range. This is most likely an issue with ESLint. (no-multiple-empty-lines - More than 1 blank line not allowed. at 7:2)
    at selectMessageRange (/Users/alex/.atom/packages/linter-xo/lib/format.js:73:10)
    at /Users/alex/.atom/packages/linter-xo/lib/format.js:24:12
    at Array.map (native)
    at /Users/alex/.atom/packages/linter-xo/lib/format.js:19:19

screen shot 2016-12-22 at 10 39 13 am

Installed packages:

atom-beautify@0.29.14
autoclose-html@0.23.0
ava@0.8.0
craft-json-snippets@1.4.0
craft-twig@0.3.2
editorconfig@2.0.5
file-icons@1.7.25
linter@1.11.18
linter-xo@0.21.2
markdown-table-formatter@2.8.4
minimap@4.25.7
@magnuslang
Copy link

I have the same issue..

@sindresorhus
Copy link
Owner

@marionebl Any ideas why this is happening? Seems like a problem with our logic.

@Arcanemagus
Copy link

no-multiple-empty-lines had a positioning bug that was fixed in v3.5.0 of ESLint, if xo is using an old enough version of ESLint it is likely still affected by this.

@sindresorhus
Copy link
Owner

It might help just reinstalling this plugin then, so you'll get a newer ESLint version.

@awcross
Copy link
Author

awcross commented Jan 10, 2017

Reinstalling seems to have fixed it.

@sindresorhus
Copy link
Owner

Cool

@awcross
Copy link
Author

awcross commented Jan 11, 2017

The issue came back after I restarted Atom. 🙁 Here's another screenshot.

screen shot 2017-01-10 at 4 06 40 pm

@awcross
Copy link
Author

awcross commented Jan 12, 2017

Ping @sindresorhus

@sindresorhus
Copy link
Owner

Check what ESLint version is being used. Probably an outdated one.

@sindresorhus sindresorhus reopened this Jan 12, 2017
@awcross
Copy link
Author

awcross commented Jan 12, 2017

Using generator-nm v3.0.1 and it was installing xo v0.16.0 and that was the problem. Once I upgraded all seems to be good now.

Thanks! 🙌🏽

@awcross awcross closed this as completed Jan 12, 2017
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

4 participants