"You can read TypeScript. Now read it in context."
The follow-on quests
TypeScript Quest is foundational. It teaches the language. Several other quests teach what to do with the language in specific contexts:
- React 19 Quest — React's component model, hooks, Server Components, Actions, in depth. Assumes TS fluency.
- Next.js Quest — full-stack TS with the App Router, server components, server actions, deployment.
- Chrome Extensions Quest — TS in the browser extension context (manifest, background workers, content scripts).
- Node.js Quest — TS on the server, Express/Hono/Fastify, deployment patterns.
- Solo Auth Quest — auth patterns in TS, OAuth, session management.
- WebSocket Quest — real-time TS, both browser and server.
Which to walk first
It depends what you want to build:
- Frontend app → React 19 Quest, then Next.js Quest.
- Full-stack from scratch → Next.js Quest covers both.
- Browser tool → Chrome Extensions Quest.
- Backend service → Node.js Quest.
- Real-time → WebSocket Quest (often paired with one of the above).
The cumulative path
Most learners walk Python Quest → TypeScript Quest → one or two framework quests. By that point you can read most of cwkPippa and build similar systems yourself. The remaining quests fill in specialized domains (AI math, ML foundations, deep-learning, etc.) — pursue whichever match your project's needs.
The Quest path is intentionally modular. TypeScript Quest is the foundation; each follow-on builds on it without re-explaining the basics. The system rewards depth — walk what you'll actually use, leave the rest for later.