The snippets, ordered obscure → unmistakable

  1. Snippet 1(Generic merger)
  2. Snippet 2(App + middleware)
  3. Snippet 3(Routes)
  4. Snippet 4(Router internals)
  5. Snippet 5(request prototype)
  6. Snippet 6(lib/express.js — entry)

Why this project gives itself away

The give-away. Snippet 1 is generic. Snippet 2's app.use(express.json()) and the (req, res, next) triple is the Express middleware signature. Snippet 3 is `app.get("/users/:id")` with route params + error-forwarding via next(err). Snippet 4 reveals layer-based router internals with layer.handle_request. Snippet 5 augments http.IncomingMessage.prototype with req.header(...) (Express's request shim). Snippet 6 is the TJ Holowaychuk / Roman Shtylman / Douglas Christopher Wilson copyright header + the canonical tagline.

How a Framed puzzle is built

Every Framed project ships exactly six snippets, hand-ordered from deeply obscure to unmistakable. The first snippet must be plausible for a dozen codebases — a generic loop, a small utility, a comment that could appear anywhere. The last snippet carries a project-specific tell: a function name, a code-comment idiom, a file header, a build invocation. Between them sit four snippets that gradually narrow the field. Reading them in order is half the puzzle: a returning Framed player learns to triangulate on indentation conventions, comment voice, naming, and the small-but-distinctive choices that betray a project's era and community.