ng lint fails after fresh install - lists no files

[Blasz]

1. OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
   Linux Ubuntu 14.04
2. Versions. Please run ng --version. If there's nothing outputted, please
   run in a Terminal:
   node --version
   And paste the result here.

$ ng --version
(node:7726) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.5
node: 6.2.1
os: linux x64

1. Repro steps. Was this an app that wasn't created using the CLI? What change did you
   do on your code? etc.

ng new foo
cd foo
ng lint

1. The log given by the failure. Normally this include a stack trace and some
   more information.

$ ng lint
(node:7613) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.

> foo@0.0.0 lint /home/vagrant/foo
> tslint "src/**/*.ts"


Lint errors found in the listed files.

1. Mention any other details that might be useful.

Not sure if this is related to the node fs/watchman lines that are output after every ng command (annoying).

[delight]

duplicate of #867 ... error is fixed with #848

you can manually edit tslint.json or wait for the next angular-cli release

[filipesilva]

Closing as duplicate, but I reopened the other issue to reflect that tslint shouldn't swallow errors as a user there commented.

[vkniazeu]

FWIW, same just happened to me with Angular 2.0.2 update.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}