Arnaud
aa6bd03c5e
Shared shopping lists (owner + collaborator-invite members) had no real-time coordination signal — no way to know someone else just checked off milk or added items while you're mid-aisle. Notifies every other member (excluding the actor) via push when an item is checked off or items are added; no-op for solo unshared lists. Deliberately skips the notifications table/notification-center (same pattern as the existing leftover-expiry cron) — this is a lightweight best-effort ping, not a persistent event, so it avoids a notification_type enum migration and a new FK column for something transient. Verified locally: added a real member to a shared list, registered a push subscription, confirmed the check-off request's added latency (945ms vs ~20ms baseline) shows the actual webpush call fired against the recipient — individual subscription failures are swallowed by design (Promise.allSettled in the existing sendPushNotification, unchanged); confirmed a solo list stays fast (no recipients to notify, true no-op).
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.