Chris Brooks

The performance hit definitely isn't noticeable, but in the CPU graph I keep in my menu bar, it is quite a jump over a natively compiled app. While this really...

This would be a great enhancement and make things much easier for us developers. Hope it gets implemented :+1:

I'm having this problem on iOS and I've tried the above workarounds, but they're not working. When using VoiceOver on iOS with the above fixes, nothing is read-out. I've checked...

Google has a backend/internal API that's undocumented but people have found and slowly figured it out, myself included. You can see some reference code here, perhaps it could be implemented....

It's my understanding that the process is spawned when a notification needs to be sent, and is closed when it disappears. I'll file this as a bug while we await...

Unsure about this, if you followed the instructions in the readme it should work fine. Possible either electron or we changed something and needs further testing.

We were planning on moving from Toast to KDE's snoretoast, but i'm unsure if this bug is limited to just the binary/program, or if it's a problem with Windows 10's...

Should be `npm install @master-aul/node-notifier`

Ah, didn't know that. Thanks! I know you can also `npm install https://github.com/master-atul/node-notifier.git` though. Bit longer, your method's better..

I'm also having this exact issue, any solutions?