Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`npm run lint` exits in error

See original GitHub issue

It is a bit scary for new users to run npm run lint because it exits in error by default if you have a violation. They usually think something is wrong with their install, where as it is just because they missed a semicolon somewhere…

Maybe we could have npm run lint exiting nicely by using the --force flag of tslint? I can submit a PR if you are OK with that.

Issue Analytics

State:
Created 7 years ago
Comments:12 (9 by maintainers)

Top GitHub Comments

1reaction

cexbrayatcommented, Jun 2, 2016

Yup, I think we agree.

Maybe we can add an explicit flag to the ng lint command in the help/documentation ? That would be a first step to help beginners and keep the current behavior.

0reactions

angular-automatic-lock-bot[bot]commented, Sep 6, 2019

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.}