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

Emits different type of error for missing declarations #141

Open
bengro opened this issue May 11, 2016 · 1 comment
Open

Emits different type of error for missing declarations #141

bengro opened this issue May 11, 2016 · 1 comment

Comments

@bengro
Copy link

bengro commented May 11, 2016

I'm using the tsify plugin for karma-browserify.

Status quo:
tsify emits an error when there is a compilation error. karma-browserify handles the error and aborts the test run when there is an error.

Problem:
The static analysis throws compilation errors for missing typings. The TypeScript compiles with errors, but the code produces it perfectly runnable and testable.

Solution:
tsify should emit different kind of type of error for errors that stem from missing declarations. That would allow tools like karma-browserify to run tests despite compilation errors.

Would that make sense from tsify point of view?

ps. If I could, I would add the declarations and typings - this does not make much sense as there are a lot of temporary fixes (using angular2 beta) and we do not have time to type all the untyped 3rd party libraries.

@bengro
Copy link
Author

bengro commented May 13, 2016

I'm willing to implement it. Do you have any pointers for me?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants