The site asks every first-time visitor for notification permission via a modal, but I never actually send push notifications. It is a permission prompt for a channel that has no traffic, and it is the first thing a visitor sees.
I want the whole dead stack gone, not just the modal:
components/layouts/components/NotificationsPrompt.tsx — the modal itself, plus its render in components/layouts/default.tsxpages/api/notification.ts — the FCM topic-subscription routefirebase/util/index.ts — the Firebase app init, only ever used by messagingpublic/firebase-messaging-sw.js — the background message service workerNOTIFICATIONS in utils/constants.ts and the public/images/notif.svg asset- the
firebase dependency in package.json, plus the now-dead NEXT_PUBLIC_FIREBASE_* and NEXT_PUBLIC_MESSAGING_TOPIC entries in .env.example
If push notifications ever come back, they should be rebuilt deliberately rather than kept alive as unused code.
The site asks every first-time visitor for notification permission via a modal, but I never actually send push notifications. It is a permission prompt for a channel that has no traffic, and it is the first thing a visitor sees.
I want the whole dead stack gone, not just the modal:
components/layouts/components/NotificationsPrompt.tsx— the modal itself, plus its render incomponents/layouts/default.tsxpages/api/notification.ts— the FCM topic-subscription routefirebase/util/index.ts— the Firebase app init, only ever used by messagingpublic/firebase-messaging-sw.js— the background message service workerNOTIFICATIONSinutils/constants.tsand thepublic/images/notif.svgassetfirebasedependency inpackage.json, plus the now-deadNEXT_PUBLIC_FIREBASE_*andNEXT_PUBLIC_MESSAGING_TOPICentries in.env.exampleIf push notifications ever come back, they should be rebuilt deliberately rather than kept alive as unused code.