What are function composition and pipe?

Q: What are function composition and pipe?

**Target Audience:** Engineers preparing for JavaScript fundamentals/functional-programming interviews. **Difficulty:** Medium > **How to read this doc:** Concepts are explained in plain language first, then tagged with 📌 Interview term: . Every numeric result below was actually run in Node. ## 1. Why This Even Matters — A Story First An assembly line where a part passes through station C, then B, then A (compose, right-to-left) produces the exact same final part as a MIRROR-IMAGE line where the same part passes through A, then B, then C in that reversed physical order (pipe, left-to-right) — as long as you also reverse the STATIONS' order to match. Same stations, same final result, just read in opposite directions — that mirror-image relationship is exactly what `compose` and `pipe` are to each other. ## 2. The Core Idea 📌 **Interview term:** `compose(...fns)` applies functions right-to-left; `pipe(...fns)` applies the same functions left-to-right — genuine mirror i

The problem

Question presented to candidate: "If compose(f, g, h)(x) and pipe(h, g, f)(x) are given, do they produce the same result? Walk me through exactly why or why not."

What a strong answer should cover:

📌 Interview term: function composition — building a new function by chaining several smaller functions together, where each one's output becomes the next one's input.
📌 Interview term: compose(...fns) — applies the functions right-to-left — the RIGHTMOST function runs first on the initial input, and each result flows leftward through the rest.
📌 Interview term: pipe(...fns) — applies the functions left-to-right — the LEFTMOST function runs first, and each result flows rightward — the mirror image of compose.
📌 Interview term: the real, direct answer to the prompt — verified directly: compose(square, addOne, double)(3) and pipe(double, addOne, square)(3) (the identical three functions, in correspondingly REVERSED order) genuinely produce the identical result (49) — confirming compose and pipe are genuinely mirror images of each other, not fundamentally different operations.
A precise answer names that function ORDER genuinely matters when the functions don't commute — verified directly: compose(square, addOne, double)(3) (49) and compose(double, addOne, square)(3) (20, the SAME three functions in a genuinely different order) produce genuinely DIFFERENT results, confirming this is not a trivial or order-independent operation.

Clarifying questions expected:

None — this is a definitional/comparison question; directly answering the prompt's own reversed-order equivalence question with real proof is the strong signal.

Code / implementation expected: Yes — a real, generic compose/pipe implementation, verified producing identical results with correspondingly reversed function order, plus a real proof that order genuinely changes the result, is the clearest demonstration.

composition

Try it yourself

Sketch your approach before you read the solution. That is what the interview tests.

Stuck? Get a hint.

A short nudge toward the approach. It will not give the answer away.

Solution

Target Audience: Engineers preparing for JavaScript fundamentals/functional-programming interviews. Difficulty: Medium

How to read this doc: Concepts are explained in plain language first, then tagged with 📌 Interview term:. Every numeric result below was actually run in Node.

1. Why This Even Matters — A Story First

An assembly line where a part passes through station C, then B, then A (compose, right-to-left) produces the exact same final part as a MIRROR-IMAGE line where the same part passes through A, then B, then C in that reversed physical order (pipe, left-to-right) — as long as you also reverse the STATIONS' order to match. Same stations, same final result, just read in opposite directions — that mirror-image relationship is exactly what compose and pipe are to each other.

2. The Core Idea

📌 Interview term: compose(...fns) applies functions ri

The solution is hidden so you can try first

6 min read · 8 sections

Run the code

Edit the code and run it here. Each console line with an expected value becomes a test.

JavaScriptReal proof: compose and pipe are genuine mirror images (identical results with correspondingly reversed order), and function order genuinely matters