The bug hunt
Find and fix five realistic bugs in your own site (a missing import, a mistyped class, a broken image path, a TypeScript prop error and the new Date() build error), each with the right tool from this module, then delete your practice branch.
Why this matters
Everything in this module so far has been one tool at a time. Real bugs don't arrive with a label saying which tool to use. You see a symptom (something missing, something red, a build that fails) and you have to decide where to look.
The five bugs in this lesson are the ones you're most likely to meet in real projects. None of them is invented for the course: every one has happened to students and to professionals, usually right after the AI made a change. Two of them break the page with an error. One breaks it silently. One hides until you build. One never shows on your laptop at all, but stops Vercel from publishing your site.
You'll plant each bug yourself, so you know it's safe. Then you'll hunt it as if you didn't know where it was: symptom first, then the right tool, then the cause, then the fix. At the end you'll delete the practice branch, and your project will be exactly as it was at the end of Module 4.
In the full lesson
- The idea in plain English
- Do it
- Check it worked
- Quick check
- What you can do now
The step-by-step, the prompt to copy, the video and the check-it-worked list, for every lesson in all 15 modules. GHS 399 ($40), paid once by mobile money or card, yours to keep.