EasyEnv

How well do you know Next.js? Prove it on the leaderboard.

One hour, a real box, and an app that will not compile. The best scores find why and get the dev server up clean. Get a score out of 100, a tier, and your rank.

Free to play. Runs in your browser. Sign in to save and share your rank.

Next.js ScoreExample
0
out of 100
Advanced
Top 13%
percentile
Compiled
challenge

Dev server up in 6m 40s. Spotted the client boundary instantly.

The challenge

Unblock the build

next dev throws before the first render: a server component reaches for a browser hook. This is the actual console you get. Find the boundary that is wrong and get the app compiling.

Next.js Challenge
59:31 left
layout.tsxapp/page.tsx
1// This runs on the server by default.← needs client boundary
2import { useState } from "react"
3
4export default function Page() {
5 const [open, setOpen] = useState(false)
6 return <button onClick={() => setOpen(!open)}>Menu</button>
7}
Terminal
$ npm run dev
○ Compiling /page ...
Error: useState only works in a Client Component.
Add the "use client" directive at the top of the file.
Build failed
Next.js App Router60 minute windowSingle real root causeFix it yourself

What we score

Outcome, root cause, restraint

Everyone gets the same broken project. The score is your judgement: did it come back to life, did you find the real cause, and was the fix clean.

1

Get it working

Outcome is graded first. A change that does not run is not a fix, however elegant it looks.

2

Find the real cause

We reward finding the actual root cause and fixing that, not patching the symptom and hoping.

3

Keep it clean

A minimal, correct change scores higher than a pile of guesses. Restraint counts.

The leaderboard

Where will you land?

Every run is judged on the same challenge, so the score is comparable. Climb from Learning to Elite, beat your friends, and share a link that shows exactly where you rank.

Claim your rank
90+
Expert
Fast, clean, every trap caught
90 - 100
75+
AdvancedExample run
Solid work, challenge shipped
75 - 89
55+
Proficient
Got there, a few detours
55 - 74
35+
Developing
Partly there, kept going
35 - 54
0+
Beginner
Made a start, room to grow
0 - 34

How it works

Three steps, one hour, one rank

01

Boot the broken stack

A real Linux machine spins up in your browser with the broken project, an editor, and a terminal. Nothing to install.

02

Fix it yourself

You have an hour. Read the logs, find the real root cause, and make the smallest change that brings it back to life.

03

Get scored and ranked

When it is live, the judge scores your run out of 100, hands you a tier, and drops you on the leaderboard.

Find out how well you really know Next.js

One broken build, one hour, one shareable rank. No setup, no install. Start in your browser right now.

FAQ

Questions, answered

It is a hands-on challenge on a real Linux machine. You fix a Next.js app that will not compile and get the dev server running. You have up to an hour, and we score the outcome, whether you found the real root cause, and how clean your change was.

No. The whole challenge runs in your browser on a real Linux box with an editor and a terminal already set up. Nothing to download, nothing to configure.

You have up to an hour, but the highest scores finish fast and clean. It is free to play. Sign in to save your result and share it.

A shareable score out of 100, a tier, and your rank against everyone else who has taken it. Send the link to a friend and challenge them to beat it.

Next.js Challenge: Fix a broken build on a real box | EasyEnv