feat(toast): enable programatically closing a toast with a specific key

[ChaserZ98]

Closes #5084

📝 Description

• change addToast(...): void to addToast(...): string where the returned string value is the unique key value of the newly created toast
• Add closeToast(key: string): void to accept a key value of string type and close the toast with the key.
• Improve doc with examples of programmatically closing toast.

⛳️ Current behavior (updates)

• No way to programmatically close one specific toast. Users can only close all of them with closeAll() method.

🚀 New behavior

• Users can now programmatically close a toast by using the toast's unique key value

💣 Is this a breaking change (Yes/No):

This should not be a breaking change IMO. Changing addToast(...): void to addToast(...): string won't have much impact on current users because it won't change the current behavior if users use it as a void method. It just provides a further option for users without breaking the current behavior.

📝 Additional Information

Summary by CodeRabbit

• New Features
  • Introduced an interactive component enabling users to create a toast, close the latest toast, or close all toasts.
  • Added a demonstration interface in the component stories to showcase toast closing functionality.
• Bug Fixes
  • Enhanced error handling for toast operations to prevent issues when the notification queue is uninitialized.
• Documentation
  • Updated the documentation with a new "Close Toast" section featuring a live code demo for improved clarity on toast management.
• Enhancements
  • Added new methods for managing toast notifications, improving overall functionality.
  • Introduced functionality for programmatically closing toast notifications using specific keys.

[changeset-bot]

🦋 Changeset detected

Latest commit: 3842fe6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@heroui/toast	Patch
@heroui/react	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

@ChaserZ98 is attempting to deploy a commit to the HeroUI Inc Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

This pull request introduces a new interactive React component for managing toast notifications, allowing users to create, close the last toast, or close all toasts. A wrapper module exports this component under a specific path. Documentation is updated with a new "Close Toast" section that demonstrates the functionality. Additionally, exports and error handling improvements have been made in the toast management source, and a new story template has been added to illustrate programmatic toast closure.

Changes

File(s)	Change Summary
apps/docs/content/components/toast/close.raw.jsx apps/docs/content/components/toast/close.ts	Added a new App component that manages toast notifications (create, close last, close all) and a wrapper that maps the component for export.
apps/docs/content/components/toast/index.ts	Imported the new close module and added a close property to the exported toastContent object.
apps/docs/content/docs/components/toast.mdx	Introduced a new "Close Toast" section with a CodeDemo referencing toastContent.close for demonstrating toast closure functionality.
packages/components/toast/src/index.ts	Added an export for the closeToast function from the toast-provider module.
packages/components/toast/src/toast-provider.tsx	Enhanced error handling in addToast and corrected closeToast to call globalToastQueue.close(key), ensuring operations occur only when the global toast queue is initialized.
packages/components/toast/stories/toast.stories.tsx	Added a new CloseToastTemplate story that demonstrates programmatically closing toasts, updated the import to include closeToast, and exported the template as CloseToast.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant App
    participant ToastProvider
    participant GlobalToastQueue

    User->>App: Click "Create Toast"
    App->>ToastProvider: addToast({ title: "New Toast", timeout: Infinity })
    ToastProvider->>GlobalToastQueue: Check if initialized & add toast
    GlobalToastQueue-->>ToastProvider: Return new toast key
    ToastProvider-->>App: Return key
    App->>App: Update state with new key

    User->>App: Click "Close The Last Toast"
    App->>ToastProvider: closeToast(lastKey)
    ToastProvider->>GlobalToastQueue: globalToastQueue.close(lastKey)
    GlobalToastQueue-->>ToastProvider: Confirm toast closed
    App->>App: Update state to remove key

    User->>App: Click "Close All Toast"
    App->>ToastProvider: closeAll()
    Note right of ToastProvider: All toasts are closed

Loading

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.

---

Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between e72a59a and 3842fe6.

📒 Files selected for processing (1)

• apps/docs/content/components/toast/close.raw.jsx (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• apps/docs/content/components/toast/close.raw.jsx

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

apps/docs/content/components/toast/close.raw.jsx (2)

1-40: Excellent demo implementation showcasing the new toast functionality

This component effectively demonstrates the three key toast operations: creating a toast, closing the last toast, and closing all toasts. The code properly tracks toast keys using React state and demonstrates how to use the newly added functionality.

One minor improvement to consider:

-        Close All Toast
+        Close All Toasts

---

23-25: Consider handling edge case more explicitly

The check for empty toast array is good, but the user experience could be improved by disabling the button when there are no toasts to close.

      <Button
+        isDisabled={toastKey.length === 0}
        onPress={() => {
-          if (toastKey.length == 0) return;
          closeToast(toastKey[toastKey.length - 1]);
          setToastKey((prev) => prev.slice(0, prev.length - 1));
        }}
      >

packages/components/toast/stories/toast.stories.tsx (1)

396-423: Well-implemented story template for the new closeToast functionality

The CloseToastTemplate effectively demonstrates how to use the new closeToast function with a stored toast key. Using useEffect for creating the toast on component mount is appropriate, and setting an infinite timeout ensures the toast remains visible for demonstration purposes.

Consider adding a check for null toast key to prevent potential errors:

          onPress={() => {
-            closeToast(toastKey);
+            if (toastKey) closeToast(toastKey);
          }}

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d8da4b7 and bece3e0.

📒 Files selected for processing (7)

• apps/docs/content/components/toast/close.raw.jsx (1 hunks)
• apps/docs/content/components/toast/close.ts (1 hunks)
• apps/docs/content/components/toast/index.ts (1 hunks)
• apps/docs/content/docs/components/toast.mdx (2 hunks)
• packages/components/toast/src/index.ts (1 hunks)
• packages/components/toast/src/toast-provider.tsx (1 hunks)
• packages/components/toast/stories/toast.stories.tsx (4 hunks)

🧰 Additional context used

🧬 Code Definitions (2)

apps/docs/content/components/toast/close.ts (1)

apps/docs/content/components/toast/close.raw.jsx (1)

• App (4-40)

packages/components/toast/stories/toast.stories.tsx (4)

packages/components/toast/src/use-toast.ts (1)

• ToastProps (23-109)

packages/components/toast/src/toast.tsx (1)

• ToastProps (16-16)

packages/components/toast/src/index.ts (4)

• ToastProps (5-5)
• addToast (9-9)
• ToastProvider (15-15)
• closeToast (11-11)

packages/components/toast/src/toast-provider.tsx (3)

• addToast (62-68)
• ToastProvider (31-60)
• closeToast (70-75)

🔇 Additional comments (8)

apps/docs/content/components/toast/close.ts (1)

1-9: Good implementation of the toast close demo!

The file correctly imports and exports the App component that showcases the new toast management functionality. This approach properly demonstrates the key features mentioned in the PR objectives: creating toasts with returned keys and closing specific toasts programmatically.

packages/components/toast/src/index.ts (1)

11-11: Correctly exports the new closeToast function!

This export makes the new closeToast function available to users, which is essential for the feature described in the PR objectives. The export follows the same pattern as the existing toast functions.

apps/docs/content/docs/components/toast.mdx (1)

112-117: Well-placed documentation for the new functionality!

The added "Close Toast" section appropriately documents the new feature that allows programmatic closing of specific toasts. Its placement in the documentation flow is logical, and using CodeDemo ensures users can see a working example.

apps/docs/content/components/toast/index.ts (1)

8-8: Proper integration of the close toast example!

The import and addition of the close module to the toastContent object correctly integrates the new close toast functionality example into the documentation system.

Also applies to: 12-12

packages/components/toast/src/toast-provider.tsx (2)

62-68: Great implementation of returning toast key!

The addToast function now returns the key from globalToastQueue.add(props), which aligns with the PR objective of enabling programmatic toast closing. The null check is also a good defensive programming practice.

---

70-75: New function looks good for closing specific toasts

The closeToast function properly implements the ability to close a specific toast by key, with appropriate null checking for globalToastQueue.

packages/components/toast/stories/toast.stories.tsx (2)

15-15: Correctly updated import statement

Import statement properly includes the new closeToast function along with existing imports.

---

530-535: Properly exported new story template

The story export follows the established pattern in the file, maintaining consistency with other examples.

[pkg-pr-new]

Open in StackBlitz

@heroui/accordion

npm i https://pkg.pr.new/@heroui/accordion@5125

@heroui/autocomplete

npm i https://pkg.pr.new/@heroui/autocomplete@5125

@heroui/alert

npm i https://pkg.pr.new/@heroui/alert@5125

@heroui/avatar

npm i https://pkg.pr.new/@heroui/avatar@5125

@heroui/badge

npm i https://pkg.pr.new/@heroui/badge@5125

@heroui/breadcrumbs

npm i https://pkg.pr.new/@heroui/breadcrumbs@5125

@heroui/button

npm i https://pkg.pr.new/@heroui/button@5125

@heroui/calendar

npm i https://pkg.pr.new/@heroui/calendar@5125

@heroui/card

npm i https://pkg.pr.new/@heroui/card@5125

@heroui/checkbox

npm i https://pkg.pr.new/@heroui/checkbox@5125

@heroui/chip

npm i https://pkg.pr.new/@heroui/chip@5125

@heroui/code

npm i https://pkg.pr.new/@heroui/code@5125

@heroui/date-input

npm i https://pkg.pr.new/@heroui/date-input@5125

@heroui/date-picker

npm i https://pkg.pr.new/@heroui/date-picker@5125

@heroui/divider

npm i https://pkg.pr.new/@heroui/divider@5125

@heroui/drawer

npm i https://pkg.pr.new/@heroui/drawer@5125

@heroui/dropdown

npm i https://pkg.pr.new/@heroui/dropdown@5125

@heroui/form

npm i https://pkg.pr.new/@heroui/form@5125

@heroui/image

npm i https://pkg.pr.new/@heroui/image@5125

@heroui/input

npm i https://pkg.pr.new/@heroui/input@5125

@heroui/input-otp

npm i https://pkg.pr.new/@heroui/input-otp@5125

@heroui/kbd

npm i https://pkg.pr.new/@heroui/kbd@5125

@heroui/link

npm i https://pkg.pr.new/@heroui/link@5125

@heroui/listbox

npm i https://pkg.pr.new/@heroui/listbox@5125

@heroui/menu

npm i https://pkg.pr.new/@heroui/menu@5125

@heroui/modal

npm i https://pkg.pr.new/@heroui/modal@5125

@heroui/navbar

npm i https://pkg.pr.new/@heroui/navbar@5125

@heroui/number-input

npm i https://pkg.pr.new/@heroui/number-input@5125

@heroui/pagination

npm i https://pkg.pr.new/@heroui/pagination@5125

@heroui/popover

npm i https://pkg.pr.new/@heroui/popover@5125

@heroui/progress

npm i https://pkg.pr.new/@heroui/progress@5125

@heroui/radio

npm i https://pkg.pr.new/@heroui/radio@5125

@heroui/ripple

npm i https://pkg.pr.new/@heroui/ripple@5125

@heroui/scroll-shadow

npm i https://pkg.pr.new/@heroui/scroll-shadow@5125

@heroui/skeleton

npm i https://pkg.pr.new/@heroui/skeleton@5125

@heroui/select

npm i https://pkg.pr.new/@heroui/select@5125

@heroui/slider

npm i https://pkg.pr.new/@heroui/slider@5125

@heroui/snippet

npm i https://pkg.pr.new/@heroui/snippet@5125

@heroui/spacer

npm i https://pkg.pr.new/@heroui/spacer@5125

@heroui/switch

npm i https://pkg.pr.new/@heroui/switch@5125

@heroui/spinner

npm i https://pkg.pr.new/@heroui/spinner@5125

@heroui/table

npm i https://pkg.pr.new/@heroui/table@5125

@heroui/tabs

npm i https://pkg.pr.new/@heroui/tabs@5125

@heroui/toast

npm i https://pkg.pr.new/@heroui/toast@5125

@heroui/tooltip

npm i https://pkg.pr.new/@heroui/tooltip@5125

@heroui/user

npm i https://pkg.pr.new/@heroui/user@5125

@heroui/react

npm i https://pkg.pr.new/@heroui/react@5125

@heroui/system

npm i https://pkg.pr.new/@heroui/system@5125

@heroui/system-rsc

npm i https://pkg.pr.new/@heroui/system-rsc@5125

@heroui/theme

npm i https://pkg.pr.new/@heroui/theme@5125

@heroui/use-aria-accordion

npm i https://pkg.pr.new/@heroui/use-aria-accordion@5125

@heroui/use-aria-accordion-item

npm i https://pkg.pr.new/@heroui/use-aria-accordion-item@5125

@heroui/use-aria-button

npm i https://pkg.pr.new/@heroui/use-aria-button@5125

@heroui/use-aria-link

npm i https://pkg.pr.new/@heroui/use-aria-link@5125

@heroui/use-aria-modal-overlay

npm i https://pkg.pr.new/@heroui/use-aria-modal-overlay@5125

@heroui/use-aria-multiselect

npm i https://pkg.pr.new/@heroui/use-aria-multiselect@5125

@heroui/use-callback-ref

npm i https://pkg.pr.new/@heroui/use-callback-ref@5125

@heroui/use-clipboard

npm i https://pkg.pr.new/@heroui/use-clipboard@5125

@heroui/use-data-scroll-overflow

npm i https://pkg.pr.new/@heroui/use-data-scroll-overflow@5125

@heroui/use-disclosure

npm i https://pkg.pr.new/@heroui/use-disclosure@5125

@heroui/use-draggable

npm i https://pkg.pr.new/@heroui/use-draggable@5125

@heroui/use-image

npm i https://pkg.pr.new/@heroui/use-image@5125

@heroui/use-infinite-scroll

npm i https://pkg.pr.new/@heroui/use-infinite-scroll@5125

@heroui/use-intersection-observer

npm i https://pkg.pr.new/@heroui/use-intersection-observer@5125

@heroui/use-is-mobile

npm i https://pkg.pr.new/@heroui/use-is-mobile@5125

@heroui/use-is-mounted

npm i https://pkg.pr.new/@heroui/use-is-mounted@5125

@heroui/use-measure

npm i https://pkg.pr.new/@heroui/use-measure@5125

@heroui/use-pagination

npm i https://pkg.pr.new/@heroui/use-pagination@5125

@heroui/use-real-shape

npm i https://pkg.pr.new/@heroui/use-real-shape@5125

@heroui/use-ref-state

npm i https://pkg.pr.new/@heroui/use-ref-state@5125

@heroui/use-resize

npm i https://pkg.pr.new/@heroui/use-resize@5125

@heroui/use-safe-layout-effect

npm i https://pkg.pr.new/@heroui/use-safe-layout-effect@5125

@heroui/use-scroll-position

npm i https://pkg.pr.new/@heroui/use-scroll-position@5125

@heroui/use-ssr

npm i https://pkg.pr.new/@heroui/use-ssr@5125

@heroui/use-theme

npm i https://pkg.pr.new/@heroui/use-theme@5125

@heroui/use-update-effect

npm i https://pkg.pr.new/@heroui/use-update-effect@5125

@heroui/aria-utils

npm i https://pkg.pr.new/@heroui/aria-utils@5125

@heroui/dom-animation

npm i https://pkg.pr.new/@heroui/dom-animation@5125

@heroui/framer-utils

npm i https://pkg.pr.new/@heroui/framer-utils@5125

@heroui/react-rsc-utils

npm i https://pkg.pr.new/@heroui/react-rsc-utils@5125

@heroui/react-utils

npm i https://pkg.pr.new/@heroui/react-utils@5125

@heroui/shared-icons

npm i https://pkg.pr.new/@heroui/shared-icons@5125

@heroui/shared-utils

npm i https://pkg.pr.new/@heroui/shared-utils@5125

@heroui/stories-utils

npm i https://pkg.pr.new/@heroui/stories-utils@5125

@heroui/test-utils

npm i https://pkg.pr.new/@heroui/test-utils@5125

commit: 3842fe6

[wingkwong]

please add changeset

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

packages/components/toast/stories/toast.stories.tsx (1)

396-436: Good implementation of the CloseToastTemplate to demonstrate the new features

This template effectively showcases the programmatic toast closing functionality with proper state management:

1. It maintains a list of toast keys using React state
2. Adds new toasts and stores their keys
3. Demonstrates closing the most recently added toast using its key
4. Shows how to close all toasts

A couple of suggestions:

1. Fix the grammar in the "Close All Toast" button:

-          Close All Toast
+          Close All Toasts

2. Consider handling the case when addToast returns null more gracefully with a user notification.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bece3e0 and e3b3549.

📒 Files selected for processing (3)

• apps/docs/content/components/toast/close.raw.jsx (1 hunks)
• packages/components/toast/src/toast-provider.tsx (1 hunks)
• packages/components/toast/stories/toast.stories.tsx (4 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• apps/docs/content/components/toast/close.raw.jsx

🧰 Additional context used

🧬 Code Definitions (1)

packages/components/toast/stories/toast.stories.tsx (4)

packages/components/toast/src/use-toast.ts (1)

• ToastProps (23-109)

packages/components/toast/src/toast.tsx (1)

• ToastProps (16-16)

packages/components/toast/src/index.ts (5)

• ToastProps (5-5)
• ToastProvider (15-15)
• addToast (9-9)
• closeToast (11-11)
• closeAll (10-10)

packages/components/toast/src/toast-provider.tsx (4)

• ToastProvider (31-60)
• addToast (62-68)
• closeToast (70-75)
• closeAll (77-87)

🔇 Additional comments (7)

packages/components/toast/src/toast-provider.tsx (3)

62-68: Good enhancement: addToast now returns the toast key

The function now correctly returns the key generated by globalToastQueue.add(), which enables programmatic closing of specific toasts. The null check for globalToastQueue is a good defensive practice that prevents potential errors.

---

70-75: Add return type for closeToast function

Consider adding a return type annotation to the function signature for consistency and improved type safety.

-export const closeToast = (key: string) => {
+export const closeToast = (key: string): void => {

---

74-74: Implementation looks good!

The closeToast implementation correctly calls globalToastQueue.close(key) to close a specific toast by its key.

packages/components/toast/stories/toast.stories.tsx (4)

15-15: Import statement updated correctly to include closeToast

The import statement has been properly updated to import the new closeToast function, which is used in the new template.

---

405-412: Good implementation for storing toast keys

The code correctly captures and stores the toast key returned from addToast, which enables closing specific toasts later. The null check before adding to the state is good defensive programming.

---

417-421: Well-implemented toast closing logic

The implementation correctly retrieves the most recent toast key and uses the closeToast function to close it, then updates the state accordingly. The empty check prevents errors when there are no toasts.

---

543-548: Use the same example as in docs

Per previous review feedback, consider aligning this example with the one used in the documentation to maintain consistency.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.changeset/slimy-beers-invent.md (1)

5-5: Grammar Improvement Suggestion.
Consider revising the message to read:
Enable programmatically closing a toast with a specific key
This minor change improves clarity and readability by including the article "a".

Here's a diff snippet for the suggested change:

-Enable programmatically closing a toast with specific key
+Enable programmatically closing a toast with a specific key

🧰 Tools

🪛 LanguageTool

[uncategorized] ~5-~5: You might be missing the article “a” here.
Context: ...e programmatically closing a toast with specific key

(AI_EN_LECTOR_MISSING_DETERMINER_A)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e3b3549 and a83f180.

📒 Files selected for processing (1)

• .changeset/slimy-beers-invent.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

.changeset/slimy-beers-invent.md

[uncategorized] ~5-~5: You might be missing the article “a” here.
Context: ...e programmatically closing a toast with specific key

(AI_EN_LECTOR_MISSING_DETERMINER_A)

🔇 Additional comments (1)

.changeset/slimy-beers-invent.md (1)

1-3: Dependency Version Bump Specified Correctly.
The changeset file correctly indicates a "minor" version bump for the @heroui/toast dependency. This aligns with the introduction of the new toast management functionality and should integrate seamlessly with the package versioning strategy.

[ChaserZ98]

I am having SB_CORE-SERVER_0007 error for storybook on my end and I don't know how to solve it. Can you check if the storybook example I updated works the same way as the docs?
Nvm, I somehow managed to do it.

[ChaserZ98]

It's been a while for this PR. Is there an expected date for the release of v2.8.0? I feel like the release pattern is really slow.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
heroui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 15, 2025 3:35pm
heroui-sb	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 15, 2025 3:35pm

[wingkwong]

@ChaserZ98 We'll have another bug fix release first. 2.8.0 includes TW4 upgrade and other breaking changes so it takes more time to review & receive feedbacks. So far we're wrapping up. I'll review your PR these days and include in beta version first. You may also consider to use the PR builds if you urgently need this feature.

[ChaserZ98]

@wingkwong Yeah, I understand that TW4 support is an urgent request but I do feel that maybe we should have a more quick release pattern for each component as long as it doesn't change the core dependencies. Instead of waiting for the release of the whole react package, it would be better to take the react package as a stable release of all the components. If anyone wants an unstable feature of a component, they could just add the latest version of that single component in their dependencies along with the stable version of the whole package. Right now, we have TW4 that is slowing down the feature release of all the components. What if there is another breaking change on other core package happening at the same time? Then probably no feature release would be made in a year.

[luixo]

@wingkwong related to this PR - can we export getToastQueue from ToastProvider?
There are methods in ToastQueue we might want to use on application level (as well as the API might update separately from HeroUI).

[wingkwong]

@luixo handled in #5476. will be included in 2.8.0 directly.