Invalid position given by 'W030'

[TotomInc]

JSHint returned a point that did not exist in the document being edited.
Rule: W030
Requested start point: 18:78

Debug information:

Atom version: 1.18.0
linter-jshint version: v3.1.4
JSHint version: jshint v2.9.5
Hours since last Atom restart: 0.1
Platform: win32
Current file's scopes: [
  "source.js",
  "meta.method-call.js",
  "meta.arguments.js",
  "punctuation.definition.arguments.end.bracket.round.js"
]
linter-jshint configuration: {
  "executablePath": "",
  "lintInlineJavaScript": false,
  "disableWhenNoJshintrcFileInPath": false,
  "scopes": [
    "source.js",
    "source.js-semantic"
  ],
  "jshintFileName": ".jshintrc",
  "jshintignoreFilename": ".jshintignore"
}

[Arcanemagus]

Is your file indented using tabs?

[TotomInc]

Yes, I always indent with tabs.

[Arcanemagus]

Please follow jshint/jshint#3151 then as this is a known issue with JSHint being broken for almost everything when using tab indentation.

[Arcanemagus]

Reopening this as a tracking issue so future users that update to v3.1.5 will get directed here and see the related JSHint issue.

If anyone is directed here and isn't using tabs to indent your file please file a new issue with a file to reproduce it on the JSHint repo, or file one here and I'll try to help you in getting one filed there where it can be fixed.

[surdu]

As far as I understanf, linter-jshint also provides the jshint tool. Couldn't you guys roll back to an older version until thy sort their stuff out ? Those messages are really annoying 😞

[Arcanemagus]

@surdu Do you know when this started breaking on their end? I'm not going to roll back the version here in the package, but it would be interesting to know when it broke. If you want to change the version you are using locally you can point the package at a different version in the settings.

The reason this only started showing up recently here is that the thing that was supposed to be showing them was broken due to a silly mistake in this package.

[surdu]

Well it strarted showing up just after your last update, but I didn't know is was not showing up before due to a bug in this package.

I'm not going to roll back the version eighter. I'll wait it our for a few days and switch to another linter if the problem will still be here.

[Arcanemagus]

I would highly recommend ESLint, it's a far better linter than JSHint. There's a reason I don't use this package myself...

[Arcanemagus]

There are reports that if you set your indent property of your JSHint configuration to 1 this issue can be worked around. If you don't have a .jshintrc file the following should work:

{
  "indent": 1
}

[Arcanemagus]

@TotomInc I'm keeping this open as a tracking issue since the package will search for an open issue before attempting to file a new one. If you would no longer like to receive notifications from this thread please click "Unsubscribe" on the right, thanks again for filing this!

[TotomInc]

Sorry for closing the issue, I thought it was resolved and you (and I) forgot to close it.

[Arcanemagus]

Nope, 8 months later and JSHint still can't handle tabs 😆.