Feat/notify level #98
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
ping @whitecolor - separated this out now |
|
ping @whitecolor - do you have time to look at these PRs please? |
|
Don't you think that this is not the responsibility of ts-node-dev? |
|
@whitecolor again - sorry for being late on this - don't know why I wasn't getting proper notifications Well, you could argue that it's not ts-node-dev's thing to integrate an OS notifier, but since that is already in place, I definitely think this is a must have personally |
|
ping @whitecolor |
|
@whitecolor ping! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Branched off #93
Fixes for specifying notifyLevel to just get errors in OS notifier
In included the fix for notifying on uncaught errors here too, since the code was related