Exposes UpdateNotificationService via providedIn: 'root'
Consumers should call MJServiceWorkerModule.forRoot({ enabled: ... })
exactly once in their root NgModule. Typically this is done internally by
MJExplorerAppModule.forRoot(environment) so MJExplorer (and downstream
Explorer-style apps) don't have to wire it themselves.
Pre-built ngsw-config.json ships at the package root; consumers point
their angular.jsonserviceWorker field at:
node_modules/@memberjunction/ng-explorer-service-worker/ngsw-config.json
If a consumer doesn't update angular.json (no SW worker built) AND
doesn't flip enabled true in their environment, this module is a no-op.
The app keeps working exactly as if the SW didn't exist.
Bundles MJ Explorer's service worker concerns into one module:
@angular/service-workerbased onenabledUpdateNotificationComponent(standalone toast)UpdateNotificationServiceviaprovidedIn: 'root'Consumers should call
MJServiceWorkerModule.forRoot({ enabled: ... })exactly once in their root NgModule. Typically this is done internally byMJExplorerAppModule.forRoot(environment)so MJExplorer (and downstream Explorer-style apps) don't have to wire it themselves.Pre-built
ngsw-config.jsonships at the package root; consumers point theirangular.jsonserviceWorkerfield at:node_modules/@memberjunction/ng-explorer-service-worker/ngsw-config.jsonIf a consumer doesn't update
angular.json(no SW worker built) AND doesn't flipenabledtrue in their environment, this module is a no-op. The app keeps working exactly as if the SW didn't exist.