How kurtiz/file-server-frontend works
Project type and purpose
• This is a React‑based Single‑Page Application (SPA) built with Vite, TypeScript and Tailwind CSS.
• It serves as the frontend for a file‑server system, handling user sign‑in, sign‑up, OTP verification and displaying a dashboard of uploaded files.
File structure
• Top‑level config: vite.config.ts, tsconfig.json/node, postcss.config.js, tailwind.config.js, .eslintrc.cjs. These define build, linting, typing and styling rules.
• Source code (‘src’):
• main.tsx + index.html: App entry point via Vite dev server.
• App.tsx + index.css: root component and global styles.
• pages/: route‑level components (SignIn, SignUp, OtpVerification, Dashboard, Error404, TestPage).
• components/: shared UI and layout pieces: Header, SideBar, ChunkCard, plus a ‘ui/’ subfolder of primitive UI controls (buttons, inputs, badges, toaster, etc.).
• lib/utils.ts and utils/authenticate.ts: helper functions for API calls, token management and authentication.
README for insights
• Confirms it’s solely the “frontend” of the File Server project.
• Run via “npm run dev” on localhost:5173 – no backend code here, so it must call external API endpoints.
Putting it all together
• Drill down: inside the SPA, show Pages → Components → UI primitives; inside the backend, show Auth vs File vs Data layers.
• Flows: sign‑in, OTP request, file upload, file listing.