Underground 2 Revived
Play Need for Speed: Underground 2 (2004) in Chrome and Firefox with WebGPU graphics, Web Audio, up to 120 fps widescreen, controller support, free roam and Online races with friends. Fan project, not
Poker with friends
Translation pending
GamesJavaScript · CSSGitHub @Severesto9286OnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
Private online poker for you and your friends, styled after GGPoker. Fake chips, real drama.Read the full README ↗Private online poker for you and your friends, styled after GGPoker. Fake chips, real drama.
client/public/audio/CREDITS.mdRequires Node 18+.
npm run install:all # installs root, server and client deps
npm run dev # server on :3001, client on :5173
Open http://localhost:5173, create a table, and share the 5-letter code. To try it alone, open a second tab with ?p=2 in the URL (each p value keeps its own session) or seat some bots:
cd server
node test/bots.js <TABLECODE> 3 # 3 bots that mostly call
node test/bots.js <TABLECODE> 4 http://localhost:3001 maniac
Run the engine tests with npm test.
Vercel can't host the game server (it needs a long-lived Socket.io process with in-memory tables and timers), so split it:
render.yaml sets everything up (root server/, node index.js). Copy the service URL, e.g. https://pokerapp-server.onrender.com.client. Add the environment variable VITE_SERVER_URL=https://pokerapp-server.onrender.com and deploy.Free Render services sleep after 15 minutes idle and take ~30–60 s to wake; the site shows "Connecting to server…" until then. A free uptime pinger (e.g. cron-job.org hitting /health every 10 minutes) keeps it awake during game nights.
The server serves the built client, so a single deployment is enough (Railway, Render, Fly.io, a VPS…). The included Dockerfile and nixpacks.toml build the client and start the server on $PORT.
Manual equivalent:
npm run build # builds client/dist
npm start # node server/index.js (serves the API, sockets and the built client)
If you'd rather host the client separately (e.g. Vercel), set VITE_SERVER_URL to the server URL before building.
server/
index.js Express + Socket.io, sessions, host commands
engine/table.js Table state machine (seats, hands, betting, run-outs, showdown, timers)
engine/evaluator.js Hand evaluation (Hold'em + Omaha)
engine/pots.js Side pots
test/ node:test suite and the bot script
client/src/
App.jsx Session + screens
lib/useGame.js Socket state, animation timeline
lib/audio.js Music playlist + sample player (assets in client/public/audio)
lib/layout.js Stage geometry and seat positions
components/ Lobby, TableView, Seat, Card, Chips, ActionBar, SidePanel
styles/ Design tokens and table/panel styles
TIMING='{"showdownHold":20000}' on the server to slow down run-outs/showdowns while debugging.