Build toast notification system

[koyelde324]

Description

Closes #20

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.

Fixes # (issue number)

Type of Change

Please delete options that are not relevant.

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📝 Documentation update
• 🎨 Style/Refactor (formatting, local variables, etc.)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

• Local manual testing (Please attach screenshots/recordings if UI changes are involved)
• Unit Tests passing (npm run test)
• Linters passing (npm run lint)
• Type check passing (npm run type-check)

AI Generation Declaration

Did you use AI (Copilot, ChatGPT, Claude, etc.) to generate any of this code?

• Yes
• No

If yes, please briefly describe which parts were generated. Reminder: You are responsible for fully understanding any AI-generated code you submit.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• I am a GSSoC participant and I have been officially assigned to the linked issue by a mentor.

[vercel]

@koyelde324 is attempting to deploy a commit to the xoxogroovy-7398's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

👋 Hey @koyelde324!

This PR doesn't appear to link to an issue. Please:

1. Make sure you're assigned to an issue first
2. Add Closes #<issue-number> to your PR description

PRs without linked issues will not be reviewed. See our Contributing Guide for details.

[github-actions]

👋 This PR has been automatically marked as stale because it has had no activity for 5 days. It will be closed in 3 days if no further activity occurs.
If you need more time, please comment to keep it open.

[Karanjot786]

Hey @koyelde324! Saw your work on GSSoC 2026.

We are building TermUI, a TypeScript terminal UI framework with React-style hooks and JSX, rendered entirely in the terminal.

We have 67 unassigned GSSoC issues open. 19 are marked good first issue. Your TypeScript background transfers directly.

• Open issues (GSSoC 2026)
• TermUI on GSSoC

Karanjot, TermUI maintainer

[koyelde324]

Hi @probably-ABHINAV,

I have completed the implementation for Issue #20 and updated the PR accordingly. Please let me know if any changes are required from my side. Looking forward to your review.

Thank you!