Fix lazy load error in Plasmo

[Xheldon]

Closes #

📝 Description

When using the HeroUI Toast component in Plasmo, there's a bug that makes the page not render. After debugging, we found it's because ToastProvider lazy loads framer-motion's domMax. Check out the related error:

PlasmoHQ/plasmo#1180
PlasmoHQ/plasmo#1241

⛳️ Current behavior (updates)

You can check the image descriptions in the two issues mentioned above. This problem causes the page to not render at all, with an error saying "xxx is not a function."

Maybe it's an issue with Parcel used by Plasmo, making it unable to dynamically import some modules. But if HeroUI could provide a usable update ASAP, developers would really appreciate it.

🚀 New behavior

Toast will work as expect.

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

No

📝 Additional Information

NO

Summary by CodeRabbit

• Refactor
  • Enhanced the efficiency of animation feature loading for toast notifications, resulting in a more seamless and responsive experience.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a596e9f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[vercel]

@Xheldon 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

The change in this pull request modifies how the ToastProvider component loads animation features. The file now statically imports domMax from framer-motion instead of using dynamic imports. Additionally, the loadFeatures function has been updated so that it immediately returns a static promise with domMax, simplifying the control flow for loading these features.

Changes

File	Change Summary
packages/components/toast/src/toast-provider.tsx	Updated the import statement to statically import domMax from framer-motion. Modified the loadFeatures function to immediately resolve with domMax, replacing the previous dynamic import mechanism.

Sequence Diagram(s)

sequenceDiagram
    participant TP as ToastProvider
    participant LF as loadFeatures
    participant DM as domMax

    TP->>LF: Call loadFeatures()
    LF->>DM: Return static reference
    DM-->>LF: Immediately resolve with domMax
    LF-->>TP: Return resolved promise with domMax

Loading

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b865356 and a596e9f.

📒 Files selected for processing (1)

• packages/components/toast/src/toast-provider.tsx (1 hunks)

🔇 Additional comments (2)

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

3-3: Good change: Static import of domMax resolves the lazy loading issue.

This change directly imports domMax from 'framer-motion' instead of dynamically importing it. This should fix the issue where Plasmo's Parcel bundler was failing with the error "xxx is not a function" when handling dynamic imports.

---

8-8: Good solution: Simplified the feature loading mechanism.

The updated loadFeatures function now returns a static Promise that immediately resolves with the already imported domMax. This eliminates the dynamic import that was causing problems with Parcel bundler in the Plasmo framework, while still maintaining compatibility with the LazyMotion component which expects a Promise.

✨ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.