You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: