Skip to content

feat: add global notifications center with activity tracking (NSOC'26)#119

Merged
Shriii19 merged 2 commits into
Shriii19:masterfrom
SrashtiChauhan:enhancement/global-notifications-center
May 28, 2026
Merged

feat: add global notifications center with activity tracking (NSOC'26)#119
Shriii19 merged 2 commits into
Shriii19:masterfrom
SrashtiChauhan:enhancement/global-notifications-center

Conversation

@SrashtiChauhan
Copy link
Copy Markdown
Contributor

NSOC'26

Overview

Implemented a modern global notifications center with activity tracking support across the dashboard.

This enhancement improves user experience by allowing users to quickly view important updates, project activity, and team actions without navigating through multiple pages.

Features Added

  • Added notifications dropdown panel
  • Added unread notification badge count
  • Added activity tracking cards
  • Added relative timestamps
  • Added mark all as read functionality
  • Added read/unread notification states
  • Added latest notification highlighting
  • Added redirect support for notification actions
  • Added outside click close behavior
  • Added keyboard accessibility support using ESC key
  • Added empty state UI
  • Added responsive and modern notification styling

Tech Stack

  • Next.js
  • React
  • Tailwind CSS

Screenshots

Screenshot from 2026-05-28 13-47-33 Screenshot from 2026-05-28 13-47-23

Issue

Closes #118

@vercel
Copy link
Copy Markdown

vercel Bot commented May 28, 2026

@SrashtiChauhan is attempting to deploy a commit to the shreemp194-gmailcom's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions
Copy link
Copy Markdown

👋 Thank you for opening this pull request! I will review your changes and assist you soon.

@SrashtiChauhan
Copy link
Copy Markdown
Contributor Author

hi @Shriii19 ,
Kindly review my pr
NSOC'26
Thank you

@vercel
Copy link
Copy Markdown

vercel Bot commented May 28, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
flow-forge Ready Ready Preview, Comment May 28, 2026 2:18pm

@Shriii19
Copy link
Copy Markdown
Owner

17:00:23.828 Running build in Washington, D.C., USA (East) – iad1
17:00:23.828 Build machine configuration: 2 cores, 8 GB
17:00:23.989 Cloning github.com/Shriii19/FlowForge (Branch: enhancement/global-notifications-center, Commit: 2d99b57)
17:00:24.576 Cloning completed: 587.000ms
17:00:24.749 Found .vercelignore
17:00:24.752 Removed 0 ignored files defined in .vercelignore
17:00:25.395 Restored build cache from previous deployment (5DbcxoScn7aEoFcwdotLxXsTcLZY)
17:00:25.666 Running "vercel build"
17:00:25.714 Vercel CLI 54.4.1
17:00:25.975 Running "install" command: npm install --no-workspaces...
17:00:34.921
17:00:34.922 added 15 packages, and audited 451 packages in 9s
17:00:34.923
17:00:34.923 153 packages are looking for funding
17:00:34.924 run npm fund for details
17:00:34.959
17:00:34.960 5 moderate severity vulnerabilities
17:00:34.960
17:00:34.961 To address issues that do not require attention, run:
17:00:34.962 npm audit fix
17:00:34.962
17:00:34.962 To address all issues (including breaking changes), run:
17:00:34.963 npm audit fix --force
17:00:34.963
17:00:34.965 Run npm audit for details.
17:00:35.017 Detected Next.js version: 16.2.6
17:00:35.018 Running "npm run build"
17:00:35.154 npm warn config ignoring workspace config at /vercel/path0/frontend/.npmrc
17:00:35.183
17:00:35.183 > frontend@0.1.0 build
17:00:35.184 > cross-env NODE_OPTIONS=--max-old-space-size=4096 next build
17:00:35.184
17:00:36.645 Applying modifyConfig from Vercel
17:00:36.666 ▲ Next.js 16.2.6 (Turbopack)
17:00:36.667
17:00:36.671 ⚠ The "middleware" file convention is deprecated. Please use "proxy" instead. Learn more: https://nextjs.org/docs/messages/middleware-to-proxy
17:00:36.709 Creating an optimized production build ...
17:00:53.342 Turbopack build encountered 1 warnings:
17:00:53.342 ./frontend/tailwind.config.ts:13:13
17:00:53.343 Module not found: Can't resolve 'tailwindcss-animate'
17:00:53.343 11 | },
17:00:53.343 12 |
17:00:53.343 > 13 | plugins: [require("tailwindcss-animate")],
17:00:53.344 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
17:00:53.345 14 | };
17:00:53.345 15 |
17:00:53.345 16 | export default config;
17:00:53.346
17:00:53.346
17:00:53.346
17:00:53.347 https://nextjs.org/docs/messages/module-not-found
17:00:53.347
17:00:53.347
17:00:53.373 ✓ Compiled successfully in 16.2s
17:00:53.385 Running TypeScript ...
17:01:01.837 Finished TypeScript in 8.5s ...
17:01:01.844 Collecting page data using 1 worker ...
17:01:02.514 Generating static pages using 1 worker (0/19) ...
17:01:02.825 Error occurred prerendering page "/forgot-password". Read more: https://nextjs.org/docs/messages/prerender-error
17:01:02.829 Error: supabaseKey is required.
17:01:02.830 at new cE (.next/server/chunks/ssr/frontend_app_lib_supabase_ts_0.he4em..js:37:45742)
17:01:02.830 at module evaluation (.next/server/chunks/ssr/frontend_app_lib_supabase_ts_0.he4em.
.js:37:50239)
17:01:02.831 at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:853:9)
17:01:02.831 at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:877:12)
17:01:02.831 at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]runtime.js:281:20)
17:01:02.831 at module evaluation (.next/server/chunks/ssr/frontend_app_forgot-password_page_tsx_00gw7q..
.js:1:87)
17:01:02.831 at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:853:9)
17:01:02.831 at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:877:12)
17:01:02.832 at Context.commonJsRequire [as r] (.next/server/chunks/ssr/[turbopack]_runtime.js:302:12) {
17:01:02.832 digest: '4016840855'
17:01:02.832 }
17:01:02.832 Export encountered an error on /forgot-password/page: /forgot-password, exiting the build.
17:01:02.857 ⨯ Next.js build worker exited with code: 1 and signal: null
17:01:02.902 npm error Lifecycle script build failed with error:
17:01:02.904 npm error code 1
17:01:02.904 npm error path /vercel/path0/frontend
17:01:02.905 npm error workspace frontend@0.1.0
17:01:02.905 npm error location /vercel/path0/frontend
17:01:02.906 npm error command failed
17:01:02.906 npm error command sh -c cross-env NODE_OPTIONS=--max-old-space-size=4096 next build
17:01:02.931 Error: Command "npm run build" exited with 1

@Shriii19
Copy link
Copy Markdown
Owner

@SrashtiChauhan you can fix above error.

@SrashtiChauhan
Copy link
Copy Markdown
Contributor Author

@SrashtiChauhan you can fix above error.

ok

@SrashtiChauhan
Copy link
Copy Markdown
Contributor Author

@SrashtiChauhan you can fix above error.

could you please now check it

@Shriii19 Shriii19 merged commit 922b092 into Shriii19:master May 28, 2026
6 checks passed
@Shriii19
Copy link
Copy Markdown
Owner

@SrashtiChauhan you can fix above error.

could you please now check it

done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Enhancement: Add Global Notifications Center with Activity Tracking (NSOC'26)

2 participants