cometchat-react-v7-push
Ground truth — DOCS-FIRST. Push is an EXTERNAL integration (Firebase/FCM + a service worker + a Dashboard FCM provider), not a UI Kit component. The full, current setup lives in CometChat's notifications docs — FETCH them, don't bake a recipe here: via
cometchat-react-v7-core/references/docs-map.md→/notifications/push-overview·/notifications/web-push-notifications·/notifications/preferences. This skill is THIN: it points you at those docs as the SOURCE and bakes ONLY the hardening deltas + the exact SDK symbols (verified vs installed@cometchat/chat-sdk-javascript). Symbols are baked; the step-by-step is fetched.
Companion skills (read first)
cometchat-react-v7-core— install, credentials,init→login→render. This skill ASSUMES it (push registers AFTER login, on the SAME SDK).
Use this skill when
"add push notifications", "web push", "notify me on a new message when the app is closed", "FCM push". For a NON-web platform (Android/iOS/RN/Flutter) push differs — that's not this skill.
Build it — FETCH the docs, then apply the deltas
- FETCH the setup from the docs (source of truth):
{DOCS_BASE}/notifications/web-push-notifications.md(+push-overview.md) viadocs-map.md. Follow its Firebase project + FCM setup, thefirebase-messaging-sw.jsservice worker, and the client registration flow. Build FROM the docs; if the docs are wrong/missing a detail, that's a DOCS gap — flag it (RULES §20), don't bake a permanent workaround. - Dashboard prerequisite: set up the FCM provider in the CometChat Dashboard (it is the SENDER). Self-hosted VAPID / a custom webhook is NOT the v7 web path. Confirm this is done or push delivers nothing.
- Install:
npm i firebase@^10.3.1(the FCM web SDK).CometChatNotificationsships with the already-installed@cometchat/chat-sdk-javascript— no extra CometChat package.