Skip to content

Conversation

@ewalid
Copy link
Owner

@ewalid ewalid commented Jan 2, 2026

Summary

Sets up the initial frontend for the project on the frontend/initial-commit branch.

Changes

  • Initialize frontend project structure
  • Configure build tooling (scripts, dependencies, configs)
  • Add base layout and root application component
  • Set up routing and initial pages/placeholders
  • Add basic styling/theme foundation
  • Add minimal README / documentation for running the frontend

How to test

  1. Install dependencies:

    • npm install
  2. Run the dev server:

    • npm run dev
  3. Open the app in your browser and verify:

    • The app builds and runs without errors
    • The initial page loads correctly
    • Basic navigation (if any) works

Notes

  • This PR is focused on project scaffolding and base structure.
  • Follow-up PRs will add actual features and business logic.

Co-Authored-By: Warp [email protected]


Note

Sets up a production-ready frontend and wires it to the existing API.

  • Adds frontend/ React + Vite app (TypeScript, Tailwind, Framer Motion) with dark mode and layout components
  • Implements translation flow: FileDropzone, language selectors, progress states, result download, and API client (POST /translate), configurable via VITE_API_URL
  • Provides hooks (useTranslate, useFileUpload, useDarkMode) and UI primitives (buttons, cards, dropdowns)
  • Configures tooling: scripts, linting, Tailwind/PostCSS, Vite dev server proxy, and example env file
  • Backend: enables CORS for http://localhost:3000, loads .env, and fixes package __init__ import

Written by Cursor Bugbot for commit cd13fb8. This will update automatically on new commits. Configure here.

@ewalid ewalid self-assigned this Jan 2, 2026
@ewalid ewalid added the enhancement New feature or request label Jan 2, 2026
Copy link

@cursor cursor bot left a 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
Copy link

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)

Fix in Cursor Fix in Web

>
<input
type="file"
accept=".xlsx,.xls"
Copy link

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)

Fix in Cursor Fix in Web

transition={{ delay: 0.5 }}
className="features-section"
>
<p className="features-text">Supports XLSX and XLS files up to 50MB</p>
Copy link

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.

Additional Locations (1)

Fix in Cursor Fix in Web

@ewalid ewalid merged commit e09bfc2 into master Jan 2, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants