Closed yoavain closed 2 years ago
My fix assumes that customPath sent in message can override the one set in the constructor
Any update on this one?
You commited package.lock
also I think the only change in the whole PR should just be
const localNotifier = options.customPath || this.options.customPath
(notifier + '-x' + (is64Bit ? '64' : '86') + '.exe');
and if you want open others pull request for other changes
I committed package-lock.json because
I can leave this PR as is, and open another one, just with the one-liner fix
I can leave this PR as is, and open another one, just with the one-liner fix
Sounds good to me, that one should hopefully gets merged more quickly 😅
Opened this PR: https://github.com/mikaelbr/node-notifier/pull/392
Fix https://github.com/mikaelbr/node-notifier/issues/377
This PR https://github.com/mikaelbr/node-notifier/pull/373 caused customPath set in WindowsToaster constructor to be ignored.
The fix is a one-liner, but I also added a test that test the entire flow using nexe