Skip to content

ng lint fails after fresh install - lists no files #1021

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Blasz opened this issue Jun 6, 2016 · 4 comments
Closed

ng lint fails after fresh install - lists no files #1021

Blasz opened this issue Jun 6, 2016 · 4 comments

Comments

@Blasz
Copy link

Blasz commented Jun 6, 2016

  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.

> [email protected] 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
Copy link

delight commented Jun 6, 2016

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

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

@filipesilva
Copy link
Contributor

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

@vkniazeu
Copy link

vkniazeu commented Oct 7, 2016

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

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants