Skip to content

deno's next build intermittently fails with 'TypeError: e[o] is not a function' while collecting page data #215

Closed

Description

@lukekarrys

deno's next build on the next fixture sometimes fails while collecting page data:

 ✓ Compiled successfully
   Collecting page data ...
TypeError: e[o] is not a function
    at t (…/suite/fixtures/next/.next/server/webpack-runtime.js:1:127)
    at 2817 (…/.next/server/chunks/961.js:2:34957)
    …
> Build error occurred
Error: Failed to collect page data for /favicon.ico

Where it's been seen

  • CI, once: run 44228515333 (PR fix: run pnpm, yarn 1 and yarn 4 the way their maintainers recommend #211, 2026-11-18). deno build-cache on next failed the prepare step's warm build, the warmup and the timed run (exit_codes: [1]). deno build in the same run passed.
  • Locally, during the 2026-11-17 audit (hotbox, x86_64, in the audit's namespace sandbox): deno build failed 3 of 3, while build-cache passed 2 of 2. Evidence: /home/luke/benchmarks-audit/audit-1117-fea5b9f6/evidence/23-build-next-ci/results/deno-build-output-*.log.
  • Passes elsewhere: deno build and build-cache passed in the 11 other CI runs checked (2026-11-17 19:40 to 2026-11-18 03:10), including main runs with 5 timed runs each, and locally in a plain sandbox (2 of 2, same deno 2.9.6). An npm-installed control build passed too.

So the failure comes and goes, but within one CI job it repeats on every attempt. It isn't specific to this machine or architecture (CI is ARM; the audit was x86).

Likely direction (unverified)

e[o] is not a function in Next's webpack runtime usually means a module id that isn't in the chunk: two copies or versions of a package in the build, or stale build output. The build/build-cache variations install without a lockfile, so deno resolves dependency versions fresh each job. A dependency version that shows up in some resolutions, or deno's node_modules/.deno layout producing duplicate copies, would explain "fails for a whole job, passes in the next". Things to check:

  • Diff deno's resolved tree (deno.lock or node_modules/.deno) between a failing and a passing job.
  • Check for duplicate react, react-dom or next copies in a failing install.
  • Rule out stale .next output (clean_build_output runs before the warm build).

Why it matters

When it fails, deno has no build/build-cache result for that day, and as #153 describes, a partial failure would be published from only the surviving runs. We also want to know the deno build numbers measure a real, complete build.

🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions