-
Notifications
You must be signed in to change notification settings - Fork 0
feat(frontend): add initial frontend setup #9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the final PR Bugbot will review for you during this billing cycle
Your free Bugbot reviews will reset on March 3
Details
You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
| "browserHash": "ef7dfdc0", | ||
| "optimized": {}, | ||
| "chunks": {} | ||
| } No newline at end of file |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Vite cache directory accidentally committed to repository
The frontend/.vite/deps/ directory contains Vite's dependency pre-bundling cache files that are auto-generated during development. These files contain machine-specific hashes and will cause cache invalidation issues when other developers pull the code. The .vite directory is missing from frontend/.gitignore and these cache files were committed by mistake.
Additional Locations (1)
| > | ||
| <input | ||
| type="file" | ||
| accept=".xlsx,.xls" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Frontend claims XLS support but backend rejects it
The frontend accepts and advertises .xls file support in multiple places (file input accept attribute, UI text, error messages), but the backend only accepts .xlsx, .xlsm, .xltx, .xltm files. Users who upload .xls files will pass frontend validation but receive a confusing "Invalid file type" error from the backend API.
Additional Locations (2)
| transition={{ delay: 0.5 }} | ||
| className="features-section" | ||
| > | ||
| <p className="features-text">Supports XLSX and XLS files up to 50MB</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Frontend advertises 50MB limit but backend enforces 10MB
The frontend claims to support files "up to 50MB" and validates against a 50MB limit, but the backend's MAX_FILE_SIZE is set to 10MB. Files between 10-50MB will pass frontend validation but be rejected by the backend with a "File too large" error, causing user confusion.
Summary
Sets up the initial frontend for the project on the
frontend/initial-commitbranch.Changes
How to test
Install dependencies:
Run the dev server:
Open the app in your browser and verify:
Notes
Co-Authored-By: Warp [email protected]
Note
Sets up a production-ready frontend and wires it to the existing API.
frontend/React + Vite app (TypeScript, Tailwind, Framer Motion) with dark mode and layout componentsFileDropzone, language selectors, progress states, result download, and API client (POST /translate), configurable viaVITE_API_URLuseTranslate,useFileUpload,useDarkMode) and UI primitives (buttons, cards, dropdowns)http://localhost:3000, loads.env, and fixes package__init__importWritten by Cursor Bugbot for commit cd13fb8. This will update automatically on new commits. Configure here.