Website for Brackt.com
bbe5bc4053
* Fix standings page team icons to use selected team avatar The full standings page was not passing avatar data (logoUrl, flagConfig, avatarType, ownerAvatarData) to StandingsPreview entries, so all teams showed the default initials fallback instead of their chosen avatar. Fetches the avatar columns from the teams table in the loader, resolves owner avatar data for teams using the owner avatar type, and threads all avatar fields through formattedStandings into previewEntries. https://claude.ai/code/session_01CVt5Vo2PDGY4G3wSWbsmRG * Add StandingsPreview component tests covering avatar rendering Tests were missing for the StandingsPreview component, which is the component that actually renders team avatars on the full standings page. Covers uploaded image, flag SVG, owner avatar inheritance, and the generated-flag fallback, plus basic content rendering (team names, owner names, points, description, full standings link). https://claude.ai/code/session_01CVt5Vo2PDGY4G3wSWbsmRG * Fix StandingsPreview test ambiguous text query for team names FlagSvg renders a <title> element with the team name for accessibility, so getByText("Team Alpha") matched two elements. Scope the query to the <p> element to target only the visible team name display. https://claude.ai/code/session_01CVt5Vo2PDGY4G3wSWbsmRG --------- Co-authored-by: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .claude | ||
| .github/workflows | ||
| .opencode/plugins | ||
| .storybook | ||
| .vscode | ||
| app | ||
| cypress | ||
| database | ||
| docs | ||
| drizzle | ||
| plans | ||
| public | ||
| scripts | ||
| server | ||
| test-fixtures/baselines | ||
| .dockerignore | ||
| .env.example | ||
| .gitignore | ||
| .npmrc | ||
| .nvmrc | ||
| .oxlintrc.json | ||
| AGENTS.md | ||
| BETTERAUTH_MIGRATION.md | ||
| CLAUDE.md | ||
| components.json | ||
| cypress.config.js | ||
| docker-compose.yml | ||
| Dockerfile | ||
| drizzle.config.ts | ||
| instrument.server.mjs | ||
| package-lock.json | ||
| package.json | ||
| plan.md | ||
| react-router.config.ts | ||
| README.md | ||
| server.ts | ||
| TESTING.md | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| tsconfig.server.json | ||
| tsconfig.vite.json | ||
| vite.config.ts | ||
| vitest.config.ts | ||
| vitest.shims.d.ts | ||
Welcome to React Router!
A modern, production-ready template for building full-stack React applications using React Router.
Features
- 🚀 Server-side rendering
- ⚡️ Hot Module Replacement (HMR)
- 📦 Asset bundling and optimization
- 🔄 Data loading and mutations
- 🔒 TypeScript by default
- 🎉 TailwindCSS for styling
- 💾 PostgreSQL + DrizzleORM
- 📖 React Router docs
Getting Started
Installation
Install the dependencies:
npm install
Development
Copy .env.example to .env and provide a DATABASE_URL with your connection string.
Run an initial database migration:
npm run db:migrate
Start the development server with HMR:
npm run dev
Your application will be available at http://localhost:5173.
Building for Production
Create a production build:
npm run build
Deployment
Docker Deployment
To build and run using Docker:
# For npm
docker build -t my-app .
# Run the container
docker run -p 3000:3000 my-app
The containerized application can be deployed to any platform that supports Docker, including:
- AWS ECS
- Google Cloud Run
- Azure Container Apps
- Digital Ocean App Platform
- Fly.io
- Railway
DIY Deployment
If you're familiar with deploying Node applications, the built-in app server is production-ready.
Make sure to deploy the output of npm run build
├── package.json
├── package-lock.json (or pnpm-lock.yaml, or bun.lockb)
├── server.js
├── build/
│ ├── client/ # Static assets
│ └── server/ # Server-side code
Styling
This template comes with Tailwind CSS already configured for a simple default starting experience. You can use whatever CSS framework you prefer.
Built with ❤️ using React Router.