Skip to content
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

How to autorun "ng lint" whenever a file is changed? #3437

Closed
thardy-pd opened this issue Dec 6, 2016 · 3 comments
Closed

How to autorun "ng lint" whenever a file is changed? #3437

thardy-pd opened this issue Dec 6, 2016 · 3 comments

Comments

@thardy-pd
Copy link

I can't seem to figure out how to cause ng serve to autorun "ng lint" whenever a js file is changed. Leaving it out of the watch functionality is basically advocating not linting at all, and I refuse to believe the angular-cli team would think so poorly of linting js source code. Please tell me I'm just missing a simple configuration somewhere!

The ability to hook whatever I want to execute when a file of a configured type is changed would be even better. I can wait on a flexible solution, but the lack of linting is downright painful for a javascript development organization.

@hansl
Copy link
Contributor

hansl commented Dec 6, 2016

Multiple editors understand tslint configurations and have plugins/extensions to perform linting as you code. Or you could watch the file system (see https://www.npmjs.com/package/node-watch) yourself and run linting when it changes.

We will not implement a watch mode for lint.

@hansl hansl closed this as completed Dec 6, 2016
@thardy-pd
Copy link
Author

The problem is that angular-cli is positioned squarely in the "watch utility" category. It REPLACES grunt and gulp. I've never had two separate watch utilities running on the same repo at one time. That sounds kinda nasty to me. I like to have one watch utility handling everything, and I think most people do.

If you're going to be THE watch utility for a repo, you need to at least provide the basics, like hooks for people to call out to whatever custom functionality they want. "Run another watch utility" is not a very good answer in my opinion.

@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

2 participants