Upabode is a small rental listing finder. It ships with 12 sample homes across Bengaluru, Pune, Hyderabad, and Kochi. Search and filters run in the browser, so the site needs no account, database, or API key.
Live site: https://naveecode.github.io/upabode/
The deploy workflow publishes the static out/ folder to GitHub Pages on every push to main.
- Text search across title, neighborhood, city, description, and amenities
- Filters for city, home type, maximum rent, bedrooms, pets, and furnished
- Sort by rent or by recently posted
- A listing detail dialog with availability and amenities
- Sample data is bundled with the page
- Next.js 16 (App Router) and React 19
- TypeScript
- Static export (
output: 'export') withbasePath/upabodefor GitHub project pages - Vitest for the search and filter functions
- GitHub Actions for lint, typecheck, unit tests, build, and Pages deploy
npm install
npm run devOpen http://localhost:3000/upabode. The /upabode prefix matches the GitHub Pages base path.
npm test
npm run lint
npm run typecheck
npm run buildnpm run build writes the static site to out/.
- A static export can only include what is known at build time. Keeping the listings in the client, and the matching rules in plain functions, meant the page could be hosted as files.
- Those functions are easier to trust once the awkward cases are tests: blank queries, combined filters, every search word required, and sorts that do not reorder the original array.
- Project pages need
basePath: '/upabode'so CSS, JavaScript, and fonts load from/upabode/_next/...instead of the domain root. - This repository already contained a larger social app (Multigram) that depends on a database, cookies, and route handlers. That cannot be a static export, so the source is preserved under
legacy/multigramrather than deleted. Credentials that had been committed in its Render config were replaced with placeholders; the old values are still in git history and should be rotated.