Dependency Hell

Every package needs a version. Every version makes demands. Pick wrong and the build burns.

Dependency Hell is a constraint puzzle about the thing every developer has fought at 2am: version conflicts.

HOW IT WORKS

Each board is a handful of packages. Choose exactly one version for each.

The catch: every version you select imposes its own requirements on the others. Select left-pad 2.0 and it suddenly demands core-utils 3.0 or higher. A requirement only applies while its version is selected — so changing one package rewires the entire board.

The dependency graph draws itself live behind the cards. Green edges are satisfied. Red, broken edges are conflicts. Turn every edge green and the build passes.

EXACTLY ONE SOLUTION. ALWAYS.

Every board is verified by exhaustive search before you ever see it. There is always exactly one valid answer — never zero, never two. No guessing. No unsolvable boards. No evenings wasted on a puzzle that never had an answer.

DIFFICULTY THAT ACTUALLY RAMPS

Starts small: three packages, two versions each. Grows to six packages and five versions, where version ranges unlock and the deduction gets genuinely hard. The levels don't run out.

FAIR BY DESIGN

No accounts. No sign-in. Nothing to register.
Your level progress and records stay on your device.
The puzzles run offline. Only the optional ads need a connection.
Ads are opt-in only. Watch one for a hint or to skip a level — or never watch one at all. Nothing interrupts you. Never a banner. Never an interstitial.
KEEP A RECORD

Levels solved. Best time. And your no-hint streak: the run you lose the moment you take a hint.

All package names are fictional. Any resemblance to a registry you have personally suffered is entirely coincidental.