Repository navigation
Releases
V1.0.5 - Add Electron Support
Root causes found:
- Singleton bridge ignored custom options — index.ts creates a default Toast() at import time via getBridge(), creating a singleton Bridge. When your code later called new Toast({ executablePath: ... }), getBridge() returned the same Bridge instance — your executablePath was never applied.
- Asar path resolution — findExecutable() used __dirname which resolves inside app.asar. Electron's patched fs.existsSync() returned true for paths inside asar, but child_process.spawn() can't execute from asar archives → ENOENT.
Fixes applied to win-native-toast package (bridge.ts):
• Added resolveAsarPath() — translates app.asar paths to app.asar.unpacked
• findExecutable() now resolves asar paths before checking existence
• start() resolves asar paths before spawning, with a helpful error message if asarUnpack is missing
• Added updateOptions() method + fixed getBridge() to apply new options to an unstarted singleton bridge
Fixes applied to gpro-delevery-server:
• package.json now points to local package (file:D:\Packages...)
• winNativeToast.mjs simplified — no more manual path resolution needed
v1.0.4 - Separate Notification and Progress Titles
Full Changelog: V1.0.2...v1.0.4
V1.0.2 - Fix duplicate progress status information under progress bar
What's Changed
- 🐛 Fixed duplicate progress status information under progress bar
Installation
npm install win-native-toast@latestView on npm: https://www.npmjs.com/package/win-native-toast
v1.0.1 - Package Improvements
What's Changed
- 📝 Added README.md to npm package (now visible on npmjs.com)
- 📄 Added LICENSE file to package
- ✨ First proper release with complete documentation
Installation
npm install win-native-toastv1.0.0
Full Changelog: https://github.com/bilooDev/win-native-toast/commits/v1.0.0