Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
node-notifier is not put in .asar.unpacked
See original GitHub issue-
Version: 19.16.0
-
Target: MacOS
I’m building an app that uses node-notifier. When in dev, it works correctly. However, once packaged, there are no notifications, and no error is thrown. It turns out that node-notifier’s included executables are not automatically detected and put in the .asar.upacked upon build, which prevents to call the executables.
As a workaround, adding "asarUnpack": ["./node_modules/node-notifier/vendor/**"] to the config works.
This problem did not happen before I bumped electron-builder from 16.1.0 to 19.16.0 .
I know this issue is similar to #1683 , but it’s not the same, as in it the executables are put in the .asar.unpacked but somehow are not executed.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@develar I’m sorry but the issue is still not obsolete. I just tested right now with the latest electron-builder, and the issue still exists. The existence of the
NotificationAPI should not in any way allow electron-builder to not do what its doc says and put executables in.asar.unpackedautomatically, just because in this specific case it happens to be a package that deals with notifications.Add “node-notifier”: “^5.3.0” to your dependencies (in addition to your devDependencies) and try to rebuild. That worked for me.