Website for Brackt.com
b81089879c
The chain (checkAndTriggerNextAutodraft) picks consecutive while_on teams immediately after a pick, but is capped at totalTeams iterations. Once the cap is hit, the next while_on team had to wait for the full timer countdown before their pick fired — which users experienced as autodraft intermittently not working. Root cause fix: the timer loop now detects while_on mode and triggers the pick immediately (≤1 s) regardless of time remaining, bypassing the countdown. A timer-update with timeRemaining:0 is emitted first so clients don't see a frozen timer. If the chain already handled the pick, executeAutoPick returns "Pick already made" and the timer moves on harmlessly. Additional fixes: - Add timerTickRunning guard so concurrent setInterval ticks (when a chain takes >1 s) don't race on the same pick slot - Use onConflictDoNothing on the draft pick INSERT in executeAutoPick so a DB unique-constraint collision is treated as "Pick already made" rather than pausing the draft - Cache draftSlots per season in the timer loop (slots never change during an active draft) — eliminates one DB query per tick - currentPickNumber || 1 → ?? 1 Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .claude | ||
| .github/workflows | ||
| .vscode | ||
| app | ||
| cypress | ||
| database | ||
| drizzle | ||
| plans | ||
| public | ||
| scripts | ||
| server | ||
| .dockerignore | ||
| .env.example | ||
| .gitignore | ||
| .mcp.json | ||
| .oxlintrc.json | ||
| 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 | ||
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.