I have the following setting in my gulpfile.js:
gulp.task('browserify', function() { browserify(config.paths.browserifyEntry) .transform(reactify) .bundle() .pipe(source('master.js')) .pipe(gulp.dest(config.paths.dist)) //.pipe(connect.reload()); }); gulp.task('watch', function () { gulp.watch(config.paths.components, ['browserify']); gulp.watch(config.paths.sassSource, ['sass']); });
All this works fine until I find the code that leads to the browser error. This happens often, because I edit the code in one file, which depends on the change that I have not made in another file yet, scrolling errors.
The problem is that when flashing errors, he finishes the viewing task. I would expect that when browsing errors, it just wonβt complete this task, but the hours will go on, so when I make other changes that will allow the browser to work successfully, it will be done. It is problematic to make changes, and then restart the browser and find that it does not work just to find that the browsing process has completed due to a browser error when your code was in an error state.
Is there a way to internalize this error so that it does not stop the viewing process? Or is there another npm package that monitors files and does not work with a browser error?
jdavis
source share