cometchat-react-push
Purpose
Web push for CometChat chat — new-message notifications when the user's tab is backgrounded or closed.
The web DOES have CometChat-native push. The JS Chat SDK ships a first-class web-push registration API: CometChatNotifications.registerPushToken(token, PushPlatforms.FCM_WEB). Paired with a Firebase Cloud Messaging (FCM) provider configured in the CometChat dashboard, CometChat's own backend delivers the push on every new message — no self-hosted push server, no web-push lib, no VAPID server of your own, and no message-sent webhook for the basic case. This is the recommended path (§1).
A self-hosted Web Push path (your own VAPID keys + push server + CometChat webhook) is documented as an advanced fallback (§7) for projects that can't or won't use Firebase. Don't reach for it unless you have to.
Not the same as the calls Web Push. Calls Web Push tries to ring the device through a closed tab (best-effort, browser-dependent). Chat push notifies on new messages — different payload + UX. Many apps need both.
Read these other skills first:
cometchat-core— provider pattern, login ordercometchat-{react,nextjs,react-router,astro}-patterns— framework-specific Service Worker registrationcometchat-react-calls/references/voip-and-web-push.md— calls-specific Web Push (overlap with this; both can coexist)cometchat-production— server-minted auth tokens