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
If you run the gulp:watch or playground tasks and make a coding error that causes a compilation failure, it stops the watch task and requires a restart. The failure seems to happen in the rollup tasks as the index.js file doesn't exist after ngc failure:
Since I would imagine this is quite a common occurrence, and it is annoying to have to keep restarting your watch/playground task mnually, it would be nice to handle compilation errors more gracefully.
The text was updated successfully, but these errors were encountered:
If you run the
gulp:watch
orplayground
tasks and make a coding error that causes a compilation failure, it stops the watch task and requires a restart. The failure seems to happen in the rollup tasks as the index.js file doesn't exist after ngc failure:[0] [11:36:43] Starting 'rollup:fesm'...
[0]
[0] events.js:160
[0] throw er; // Unhandled 'error' event
Since I would imagine this is quite a common occurrence, and it is annoying to have to keep restarting your watch/playground task mnually, it would be nice to handle compilation errors more gracefully.
The text was updated successfully, but these errors were encountered: