karma-runner/karma

[Question] Can you access preprocessor errors programatically?

Open

#2 064 ouverte le 20 avr. 2016

Voir sur GitHub
 (9 commentaires) (1 réaction) (0 assignés)JavaScript (11 918 stars) (1 703 forks)batch import
help wantedtype: bug

Description

I'm running karma programatically through the Server API and was wondering if there was a good way catch preprocessor errors when they occur.

Right now, if a preprocessor (babel for example) fails, I'll just see a message logged from Karma, but the server will still start up.

I'd like to be able to cancel the whole process, or at least catch the error when it occurs. I tried tracing my way through the source, and couldn't exactly understand what happens when a preprocessor invokes it's callback with an error: https://github.com/karma-runner/karma/blob/master/lib/preprocessor.js#L26

Any advice?

Guide contributeur

Stack technique
javascriptnodejs
Domaine
testingdeveloper experience
Type d'issue
feature
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
3
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
1-3 hours
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
stale
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
mostly clear
Prérequis
Familiarity with Node.jsUnderstanding of Karma's preprocessor systemBasic knowledge of error handling in callbacks
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
30
Direction de recherche
Examine the Karma source code, especially lib/preprocessor.js (line 26) to understand how preprocessor errors are currently handled. Look at the Server API documentation and see if there are events or hooks to capture errors. Consider proposing a new event or callback modification. Since the issue is from 2016, check if later versions have addressed this. The linked file shows that the done callback is called with an error object; investigate how that error propagates.