-
Notifications
You must be signed in to change notification settings - Fork 12k
Please provide an option in config to ignore errors #5638
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
Comments
I would say this is even more important for serve command, during the development. I don't think there is an error what you could not fix for the build (by casting, maybe even to any, or adding extra typings). It is a very bad practice to allow your production build with errors. |
But there are such errors.
Each project and each team should have own rules. "Bad/good practices" are just sets of advices, not laws. |
Not needed anymore after #5698, thanks. |
I am looking for a way to continue a build even with errors. e-oz, is there a way to specify this in config? The error I'm getting is "ERROR in Cannon read property 'getSourceFile' of undefined' which does not reference any file, and I have been unable to fix it. It seems to maybe be an issue in WebPack with Windows systems. I'd like to just IGNORE the error and continue the build... |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug Report or Feature Request (mark with an
x
)Versions.
1.0
Please create an option to don't break compilation if there are errors during compilation. Some errors are not critical, some are produced by stupidity of compiler/linter, but build still should be created. It's extremely important for existing apps. Currently we can't use AngularCLI 1.0 because of minor error, produced by variable compiler can't see (created in template). Nobody cares about this error and it works just fine with previous version (in runtime too).
The text was updated successfully, but these errors were encountered: