Vals-Smith

/ vercel / next.js

PUBLIC

Updated 7/19/2026

The React Framework

2168 Branches 34775 Commits 4113 Contributors 74 Tasks

Key Takeaways

  • GPT-5.6 Sol leads with 55 of 74 tasks resolved, narrowly ahead of Kimi K3 at 54.
  • Grok 4.5 is the strongest value option, resolving 50 tasks for $0.99 per test in 322 seconds.
  • GPT-5.6 Sol and Kimi K3 resolve 59 of 74 tasks together, showing complementary strengths beyond their adjacent leaderboard positions.

Cost / Test vs. Accuracy

Grok 4.5 gives up five tasks relative to GPT-5.6 Sol but cuts cost per test from $2.51 to $0.99.

Latency vs. Accuracy

Grok 4.5 resolves 50 tasks in 322 seconds, compared with 55 tasks in 508 seconds for GPT-5.6 Sol. The faster GPT-5.6 Terra run resolves only 34 tasks.

Average token use / test

Input
Output
Reasoning
Cache read
Cache write
Claude Sonnet 5
10.8M
Claude Opus 4.7
6.0M
Claude Opus 4.8
5.8M
Claude Fable 5
5.3M
GLM 5.2
4.4M
Kimi K3
3.8M
GPT-5.6 Luna
3.6M
Gemini 3.5 Flash
2.9M
Muse Spark 1.1
2.4M
Claude Haiku 4.5 (Nonthinking)
2.3M
GPT 5.5
2.3M
GPT-5.6 Sol
2.2M
Grok 4.5
1.4M
Gemini 3.1 Pro Preview (02/26)
1.1M
GPT-5.6 Terra
772K

Tasks with failures

PassedFailed

Task detail

143926d6a2c2

Issue statement

When a Next.js project sets output: 'export' (or output: 'standalone') and also enables the experimental supportsImmutableAssets flag, the flag is incorrectly left enabled in the resolved configuration.

supportsImmutableAssets is designed to work together with the adapter code path, which controls how static assets are emitted (e.g. under a versioned _next/static/immutable/ directory). The output: 'export' and output: 'standalone' modes currently use a non-adapter code path, so honoring supportsImmutableAssets there produces incorrect output.

Expected behavior: while resolving/normalizing the Next.js configuration, if experimental.supportsImmutableAssets is enabled but output is set to 'export' or 'standalone', the flag must be force-disabled (experimental.supportsImmutableAssets === false) in the final resolved config, even when the user explicitly requested true. When output is not one of those values, an explicitly enabled supportsImmutableAssets must remain enabled.

This resolution should happen as part of the same config finalization that applies other framework defaults, so it is reflected in the config returned by loading the configuration.

Hidden tests
diff --git a/test/unit/isolated/supports-immutable-assets-output.test.ts b/test/unit/isolated/supports-immutable-assets-output.test.tsnew file mode 100644index 00000000..e80a1c84--- /dev/null+++ b/test/unit/isolated/supports-immutable-assets-output.test.ts@@ -0,0 +1,45 @@+/* eslint-env jest */+import { PHASE_PRODUCTION_BUILD } from 'next/constants'++// force require usage instead of dynamic import in jest+// x-ref: https://github.com/nodejs/node/issues/35889+process.env.__NEXT_TEST_MODE = 'jest'++describe('config - supportsImmutableAssets with output', () => {+  let loadConfig: typeof import('next/dist/server/config').default++  beforeEach(async () => {+    jest.resetModules()+    const configModule = await import('next/dist/server/config')+    loadConfig = configModule.default+  })++  it('force-disables supportsImmutableAssets when output is "export"', async () => {+    const config = await loadConfig(PHASE_PRODUCTION_BUILD, '<rootDir>', {+      customConfig: {+        output: 'export',+        experimental: { supportsImmutableAssets: true },+      },+    })+    expect(config.experimental.supportsImmutableAssets).toBe(false)+  })++  it('force-disables supportsImmutableAssets when output is "standalone"', async () => {+    const config = await loadConfig(PHASE_PRODUCTION_BUILD, '<rootDir>', {+      customConfig: {+        output: 'standalone',+        experimental: { supportsImmutableAssets: true },+      },+    })+    expect(config.experimental.supportsImmutableAssets).toBe(false)+  })++  it('keeps supportsImmutableAssets enabled when output is not set', async () => {+    const config = await loadConfig(PHASE_PRODUCTION_BUILD, '<rootDir>', {+      customConfig: {+        experimental: { supportsImmutableAssets: true },+      },+    })+    expect(config.experimental.supportsImmutableAssets).toBe(true)+  })+}) 

Head-to-head

VS

Accuracy

74.32%Δ 1.35%

72.97%

Cost / test

$2.51Δ $9.22

$11.73

Latency

508sΔ 495s

1004s

Cost distribution

$0.00$22.16$44.31

Latency distribution

0s1899s3799s

Input token distribution

09.2M18.4M

Output token distribution

050.2K100.3K

Task outcomes

74 tasks

Both
A only
B only
Neither