Added vite error handler to resolve post build error

[akhilmhdh]

Description 📣

This resolves a vite error that happens on post deployment. Fixed by following vite doc.
Reference: https://vite.dev/guide/build#load-error-handling

Type ✨

• Bug fix
• New feature
• Improvement
• Breaking change
• Documentation

Tests 🛠️

# Here's some code block to paste some code snippets

---

• I have read the contributing guide, agreed and acknowledged the code of conduct. 📝

Summary by CodeRabbit

• New Features
  • The application now triggers an automatic page refresh when a preload error occurs, reducing downtime from resource load issues. This provides a more resilient user experience, particularly when encountering unexpected page interruptions during navigation or interaction. With this change, the application maintains consistently reliable performance even under unforeseen loading conditions.

[coderabbitai]

Walkthrough

The changes introduce an event listener for the "vite:preloadError" event within the Vite development environment. When this event is triggered, the application will execute a page reload to handle possible preload errors during development. Additionally, a comment has been added to reference the Vite documentation for load error handling, providing context for this implementation. There is also a minor formatting update to an existing comment, where a trailing slash has been added. No modifications were made to the public or exported entities.

Tip

CodeRabbit's docstrings feature is now available as part of our Pro Plan! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 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 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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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 (1)

frontend/src/main.tsx (1)

24-27: Implementation for handling Vite preload errors looks good, but URL needs correction.

The error handling implementation follows Vite's recommended approach for handling preload errors, which should help resolve the post-build error mentioned in the PR objectives.

However, there's a small issue with the documentation URL - it should be "vitejs.dev" instead of "vite.dev".

-// https://vite.dev/guide/build#load-error-handling
+// https://vitejs.dev/guide/build#load-error-handling

Also, consider whether the comment "for example, refresh the page" should be removed since it suggests this is copied example code rather than a finalized implementation.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f4bd48f and e9dd334.

📒 Files selected for processing (1)

• frontend/src/main.tsx (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Check Frontend Type and Lint check

🔇 Additional comments (1)

frontend/src/main.tsx (1)

22-22: Minor formatting change noted.

The trailing slash added to this comment appears to be a minor formatting adjustment that doesn't affect functionality.