js_notifications

Releases

1. ▸▾1.0.026 Jul 2026

   feat: Add WASM support with web package by @cybex-dev in #2

   What's Changed

   • feat: Add WASM support with web package by @cybex-dev in #2
   • fix: update badge to String? by @cybex-dev in #3
   • feat: add bundled service worker by @cybex-dev in #4

   Full Changelog: 0.0.5...1.0.0

   Open source →

   Additional notes

   • Zero-setup service worker: js_notifications-sw.js now ships as a bundled Flutter asset of the package (deployed at assets/packages/js_notifications/assets/) and is registered automatically — manually copying the file into your app's web/ folder is no longer required. Existing copied files can be deleted; legacy registrations are unregistered automatically on startup.
   • Service worker URL now resolves against the document base URI, fixing deployments under a non-root <base href>.
   • ServiceWorkerManager is now a singleton (ServiceWorkerManager.instance, or the factory constructor to assign event callbacks) — a page has one service worker registration, and the manager owns the listeners attached to it.
   • Service worker setup moved out of the ServiceWorkerManager constructor into an explicit, idempotent init(). The plugin calls it automatically on registration and exposes initialize() (returns whether the worker registered) and isInitialized. Notifications posted before initialisation completes now wait for it instead of being dropped with "No service worker ready".
   • Added registerServiceWorker({url, scope}) — replace the bundled worker with a custom script (e.g. custom sendAction handling), register the bundled worker under a custom scope, or both. The scopeUrl setter now works (previously ineffective): it re-registers the current worker under the new scope. Note: scopes outside the worker script's directory require a Service-Worker-Allowed response header from the server.
   • Fixed: service worker updates are now adopted. When a byte-different worker was deployed, the plugin kept posting to the previous (now redundant) worker and notifications silently stopped working until a page reload. Updates are tracked via updatefound on the plugin's own registration; the new worker is adopted once it reaches activated, with a redundant fallback to the registration's active worker.
   • Fixed: controllerchange no longer adopts navigator.serviceWorker.controller. The controller is the worker controlling the page — never this plugin's worker, whose scope controls no pages — so a controller change (e.g. Flutter's own flutter_service_worker.js updating) could redirect postMessage to a worker that ignores the plugin's protocol.
   • Fixed service worker script bugs: error-logger shadowing in the showNotification catch handler, console.warn argument spreading; renamed SW log tag callkit_sw → js_notifications_sw.
   • WebAssembly support: full migration off deprecated dart:html to package:web + dart:js_interop — the package now compiles with flutter build web --wasm.
   • BREAKING: badge is now String? — the URL of the monochrome badge image, per the Web API's Notification.badge (previously mistyped as int?, which browsers ignored; not to be confused with the numeric Badging API, navigator.setAppBadge).
   • BREAKING: vibrate is now List<int>? (previously web.VibratePattern?); package:web types no longer appear in the public API.
   • BREAKING: minimum Flutter version raised to 3.22 (stable WASM toolchain floor).
   • BREAKING: SWEvents constants for events that never dispatch on page-side objects were removed (push, pushsubscriptionchange, sync, install, activate, fetch — these fire inside the worker's own global scope); updatefound was added.
   • Internal: service worker event wiring now uses EventStreamProvider subscriptions; removed ~10 dead no-op event listeners that never fired on page-side objects. ServiceWorkerManager.dispose() now cancels and clears every subscription and resets state, so init() can run again afterwards.
   • Added deepCastMap/deepCastValue helpers (lib/utils/utils.dart) used to normalise dartify() output into the Map<String, dynamic> shape the plugin uses for event payloads.
   • Added bundledSwAssetPath and bundledSwAssetDirMarker constants; defaultScope is retained for legacy-registration migration.
   • isSupported now feature-detects the Notification global (dart:html's Notification.supported has no package:web equivalent).
   • Note: under the WASM runtime, integral JS numbers in notification data payloads may be delivered back to Dart as double — treat round-tripped numbers as num.