If an import path does not resolve to an existing file, the linter throws an exception, rather than logging a proper error message:
ERROR finding /home/ben/Projects/foo/foo-element.html
Error: ENOENT: no such file or directory, open '/home/Projects/foo/foo-element.html'
at Error (native)
This makes it difficult to integrate the linter with IDEs that parse linter output (eg, vim+syntastic), since a missing file crashes the linter and all other errors and warnings are swallowed (also, the line/col is not reported).
The error should instead read:
my-app.html:4:0
could not find file referenced in import 'foo-element.html'
If an import path does not resolve to an existing file, the linter throws an exception, rather than logging a proper error message:
This makes it difficult to integrate the linter with IDEs that parse linter output (eg, vim+syntastic), since a missing file crashes the linter and all other errors and warnings are swallowed (also, the line/col is not reported).
The error should instead read: