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

Error linting file ended with space #1036

Closed
doodlewind opened this issue Dec 27, 2017 · 2 comments

Comments

@doodlewind
Copy link

commented Dec 27, 2017

Hi, standard cli works great while it throws error linting following file:

foo.js.zip

➜  SideBar standard foo.js
standard: Unexpected linter output:

RangeError: Line number out of range (line 4 requested, but only 3 lines present).
    at SourceCode.getIndexFromLoc (/Users/ewind/.nvm/versions/node/v8.3.0/lib/node_modules/standard/node_modules/_eslint@3.19.0@eslint/lib/util/source-code.js:389:19)
    at Object.fix (/Users/ewind/.nvm/versions/node/v8.3.0/lib/node_modules/standard/node_modules/_eslint@3.19.0@eslint/lib/rules/no-multiple-empty-lines.js:116:52)
    at RuleContext.report (/Users/ewind/.nvm/versions/node/v8.3.0/lib/node_modules/standard/node_modules/_eslint@3.19.0@eslint/lib/rule-context.js:127:34)
    at Program:exit.allLines.reduce.concat.reduce (/Users/ewind/.nvm/versions/node/v8.3.0/lib/node_modules/standard/node_modules/_eslint@3.19.0@eslint/lib/rules/no-multiple-empty-lines.js:108:37)
    at Array.reduce (<anonymous>)
    at EventEmitter.Program:exit (/Users/ewind/.nvm/versions/node/v8.3.0/lib/node_modules/standard/node_modules/_eslint@3.19.0@eslint/lib/rules/no-multiple-empty-lines.js:93:22)
    at emitOne (events.js:120:20)
    at EventEmitter.emit (events.js:210:7)
    at NodeEventGenerator.applySelector (/Users/ewind/.nvm/versions/node/v8.3.0/lib/node_modules/standard/node_modules/_eslint@3.19.0@eslint/lib/util/node-event-generator.js:265:26)
    at NodeEventGenerator.applySelectors (/Users/ewind/.nvm/versions/node/v8.3.0/lib/node_modules/standard/node_modules/_eslint@3.19.0@eslint/lib/util/node-event-generator.js:294:22)

If you think this is a bug in `standard`, open an issue: https://github.com/standard/standard/issues

This file is ended with a space instead of a line break. Any ideas validating such input format?

@RyanFilho

This comment has been minimized.

Copy link

commented Jan 3, 2018

I downloaded the standard for the first time and I'm also having this problem:

/Development/book-by-isbn$ standard
standard: Unexpected linter output:

RangeError: Line number out of range (line 20 requested, but only 19 lines present).
    at SourceCode.getIndexFromLoc (/home/unknown/.nvm/versions/node/v8.9.3/lib/node_modules/standard/node_modules/eslint/lib/util/source-code.js:389:19)
    at Object.fix (/home/unknown/.nvm/versions/node/v8.9.3/lib/node_modules/standard/node_modules/eslint/lib/rules/no-multiple-empty-lines.js:116:52)
    at RuleContext.report (/home/unknown/.nvm/versions/node/v8.9.3/lib/node_modules/standard/node_modules/eslint/lib/rule-context.js:127:34)
    at Program:exit.allLines.reduce.concat.reduce (/home/unknown/.nvm/versions/node/v8.9.3/lib/node_modules/standard/node_modules/eslint/lib/rules/no-multiple-empty-lines.js:108:37)
    at Array.reduce (<anonymous>)
    at EventEmitter.Program:exit (/home/unknown/.nvm/versions/node/v8.9.3/lib/node_modules/standard/node_modules/eslint/lib/rules/no-multiple-empty-lines.js:93:22)
    at emitOne (events.js:121:20)
    at EventEmitter.emit (events.js:211:7)
    at NodeEventGenerator.applySelector (/home/unknown/.nvm/versions/node/v8.9.3/lib/node_modules/standard/node_modules/eslint/lib/util/node-event-generator.js:265:26)
    at NodeEventGenerator.applySelectors (/home/unknown/.nvm/versions/node/v8.9.3/lib/node_modules/standard/node_modules/eslint/lib/util/node-event-generator.js:294:22)

If you think this is a bug in `standard`, open an issue: https://github.com/standard/standard/issues

@feross feross added the bug label May 9, 2018

@feross

This comment has been minimized.

Copy link
Member

commented May 9, 2018

Hey! Sorry for the delay in responding to this issue.

This crash was fixed in standard v11.0.0 which was released 3 months ago.

@feross feross closed this May 9, 2018

@lock lock bot locked as resolved and limited conversation to collaborators Aug 7, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
3 participants
You can’t perform that action at this time.