-
Notifications
You must be signed in to change notification settings - Fork 32
Error: Column start (x) greater than line length (0) #249
Comments
@mzahor Are you able to share a JS file that triggers this, as well as the relevant configuration file? The error should be reported to node-jscs, and for that matter the Uploading a zip file like this would be ideal. |
@eviljoe, @kfwerf, and @alexmt as you have all 👍 this issue, I'm assuming you are seeing issues like this as well. The above instructions apply equally as well to you, but can you please file an issue of your own as often these bugs are unique since the error above is just a generic "the linter gave a range that is impossible" message. So far I know there are issues with the |
@Arcanemagus attaching zip with source code and |
The only column start bug I could find was related to this: {
"disallowPaddingNewlinesInBlocks": true,
"requirePaddingNewLineAfterVariableDeclaration": true
}
let foo = 42;
function bar() {
let foobar = 42;
} The crashing error seems to be able to be reduced down to this: {
"disallowUnusedParams": true,
"requirePaddingNewLineAfterVariableDeclaration": true
}
let foo = false;
function bar($foobar) {} I'll file issues on node-jscs referencing this and we'll see what the actual issue is. |
Closing as fixed in jscs-dev/node-jscs#2252. |
Version
4.0.0
Issue
Constantly getting this error when editing js files:
Screenshot:
Also getting this error, not sure it's related to this issue:
The text was updated successfully, but these errors were encountered: