Remove unused WhatsApp HTML files and update Vite configuration to el…

[MoussaGerges9]

…iminate references

Summary by CodeRabbit

• Chores
  • Removed separate WhatsApp build entry point and configuration files
  • Streamlined build system to use default input handling

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ff7d359e-4a28-489f-a80e-2b1926776dc9

📥 Commits

Reviewing files that changed from the base of the PR and between 79b1dc3 and 3924f03.

📒 Files selected for processing (3)

• frontend/build/whatsapp/index.html
• frontend/vite.config.mjs
• frontend/whatsapp/index.html

---

📝 Walkthrough

Walkthrough

The changes remove WhatsApp-related HTML entry points and their corresponding build configuration. Two HTML shell files from the frontend source and build directories are deleted, and the Vite build configuration is simplified by removing multi-entry Rollup setup that previously supported separate main and WhatsApp builds.

Changes

Cohort / File(s)	Summary
WhatsApp HTML Entry Points frontend/whatsapp/index.html, frontend/build/whatsapp/index.html	Deleted HTML bootstrap files that served as WhatsApp entry points, removing document structure, meta tags, favicon/manifest links, and script loaders.
Build Configuration frontend/vite.config.mjs	Removed path.resolve import and Rollup multi-entry input configuration, simplifying the build to use default inputs instead of explicit main/whatsapp entries.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• Fixing whatsapp static page linking problem #54: Directly inverse relationship — adds back the WhatsApp HTML entry files and restores the Rollup multi-entry configuration that this PR removes.

Poem

🐰 The WhatsApp door now gently closes,
No more HTML shells where green prose is,
Config simplified, build paths made clear,
One less entry point to steer—
Clean slate awaits next frontier! 📱✨

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch development

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR simplifies the Vite build configuration by removing the multi-page application (MPA) setup for the /whatsapp route. The WhatsAppForm component is already served through React Router as part of the single-page application, making the separate whatsapp/index.html entry point redundant.

Changes:

• Removed the source and built whatsapp/index.html files that served as a separate Vite entry point
• Simplified vite.config.mjs by removing the rollupOptions.input multi-entry configuration and the unused path import

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
frontend/whatsapp/index.html	Removed redundant source MPA entry point for the WhatsApp route
frontend/build/whatsapp/index.html	Removed the corresponding built output HTML file
frontend/vite.config.mjs	Removed rollupOptions multi-entry config and unused resolve import from path

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.