Description
Version
3.0.4
Node and OS info
Node v9.4.0, npm v5.6.0, Windows 10
Steps to reproduce
- Install
@vue/cli
on Windows - Run
vue ui
on a project - Install/update/etc a dependency in the UI
- Note that no notification was triggered and that
%APPDATA%\Microsoft\Windows\Start Menu\Programs
now has a SnoreToast shortcut
- Note that no notification was triggered and that
- Install/update/etc another dependency
- Note that a notification was triggered successfully
What is expected?
SnoreToast would not have a shortcut since the user may not like its addition to their start menu without indication of its purpose.
Additionally, the notification should trigger the first time, but I'm guessing this is caused by SnoreToast failing to notify without an app ID in the start menu to use for the notification.
What is actually happening?
The shortcut is installed without an opt-in, notification fails the first time
The UI's notification API uses node-notifier
which in turn uses SnoreToast
for native Windows notifications.
SnoreToast seems to indicate that a program in the start menu is necessary for notifications, though I can't find anything to back up that it needs to be in the start menu in case SnoreToast can be used from the node_modules
folder.
If the CLI was an Electron app, the intended use of node-notifier
would be to use the shortcut for the CLI instead (which would fix also fix the issue with it not firing and it saying the wrong app name when notifying). Since there isn't a shortcut for the CLI, it sounds like a workaround would need to be found to keep the implementation the same.
The issue with it not firing the first time is most likely related to and could be fixed by "installing" the shortcut before the first notification.