Closed nandak522 closed 8 years ago
This is almost certainly a bug in the esprima
parser used by jshint
. If you want us to verify that you'll need to send the file you were seeing this on somewhere we can access it, but it's unlikely this is necessary.
You might want to look into moving to a linter that supports alternative parsers like eslint
or jscs
.
Ok. Let me install linter-eslint and give it a shot. Thanks :+1:
On Thu, 4 Feb 2016 at 01:01 Landon Abney notifications@github.com wrote:
This is almost certainly a bug in the esprima parser used by jshint. If you want us to verify that you'll need to send the file you were seeing this on somewhere we can access it, but it's unlikely this is necessary.
You might want to look into moving to a linter that supports alternative parsers like eslint or jscs.
— Reply to this email directly or view it on GitHub https://github.com/atom-community/linter/issues/1062#issuecomment-179417417 .
Switched to eslint and couldn't be more happier :+1:
[Steps to reproduce below:]
Atom Version: 1.4.2 System: Ubuntu 14.04.3 Thrown From: linter package, v1.11.3
Stack Trace
Uncaught TypeError: Invalid Point: (565, NaN)
Commands
Config
Installed Packages