Backtestsvuerun-20261007-145226#15465

Issue #15465 Merged fix PR # Run 7 Oct 2026 · run-20261007-145226 vuejs/core

[compiler-sfc] Typo 'exit' instead of 'leave' in estree-walker causes missing ASI guard and runtime error with consecutive awaits

Better

Our patch was judged better than the merged fix.

In this judgment, Patch A = our agent, Patch B = the merged fix.

Both patches make the identical source change in compileScript.ts, renaming `exit` to `leave` so estree-walker actually calls the hook and pops the scope stack when leaving a BlockStatement. That is the root-cause fix the issue identifies, so correctness is equal and the decision rests on the tests.

Patch A adds two snapshot-style regex assertions. The first scenario is a nested `if` block followed by two awaits inside an outer block. The second is a nested `for` loop block followed by two awaits. Both check that the leading `;(` ASI guard appears before the second `_withAsyncContext` call. The first test also checks the guard before the first await that follows the nested block's closing `}`. Before the fix, the unpopped inner block stays on top of the scope stack, so `needsSemi` evaluates false and these assertions fail. After the fix they pass. This matches the existing `toMatch`-based style of the surrounding await tests, covers two kinds of nested block, and checks the exact output property the issue describes.

Patch B's test executes the compiled output at runtime through `new Function`, with a stubbed `_withAsyncContext`. It strips imports using a non-multiline `^import .*\n` regex, which only removes the first line. It also relies on `genDefaultAs` producing no `export` statement, the exact shape of the setup return value (`{}`), and the `expose` call signature. It does reproduce the reported TypeError directly, but it is more fragile, unconventional for this spec file, and covers only one scenario.

With identical fixes, Patch A's tests are more robust, more consistent with the surrounding conventions, and slightly broader in coverage.

The judge saw only the two patches, labelled A and B in random order, with issue links and version numbers removed. The reasoning above is shown verbatim.

Solve

4m 37s

Wall-clock time in the container

Full test suite

No new failures

3,721 passed · 6 skipped · 3,727 total

Contamination audit

Clean

No sign the agent saw the real fix

Patch size

34vs 21 merged

Changed lines, ours vs merged

Vue version

3.5.40

Link to minimal reproduction

https://play.vuejs.org/#eNp9kk9PAyEQxb/KhIttUln/xYNumqjxoAc12ngiMevuuEVZIDBsa0y/u8M21h60J8j8HsN7A1/iwnvZJxRnoox10J4gIiU/VbYo4FDChf0Ei5GwgVfj6g8Y+RTnGIEcxNp5nMBrIpb0GMA7H6FJmCHNkUk7Vla/wYhCwjF8KQtQOxudQWlcO9rbbr3H2pWyw81HEmYLN2ixTqT73NPvG77GQLWoNEVlhxUegut0RBmQ2/Y4Ohyf/4eOMiqLdVCOWBJ23lSE07LR/XTGZsoi78piQ8REEAe1b7qV79FZntQQQ4nadV4bDPeeNPtU4mwdMLPKGLe4HWo5+uSnXs+x/vij/h6XuabEA3vF0KMSG0ZVaJHW+PrpDpe838DONcmwegd8zOl5hs6uZZfJNmx7Sze4vem8C6RtO4vXS0Ibf0Jlo1m5GvRK8He52hH91+6xPBnO8bPyFF8oPmPIXXmEp/JAHovVNzTb1oo=

Steps to reproduce

  1. Open the SFC Playground link.
  2. Click on the "JS" tab in the right panel to view the compiled output.
  3. Observe the compiled code for the two await statements.
  4. Notice that there is no semicolon (;) inserted between the two _withAsyncContext blocks.

What is expected?

  1. Open the SFC Playground link.
  2. Click on the "JS" tab in the right panel to view the compiled output.
  3. Observe the compiled code for the two await statements.
  4. Notice that there is no semicolon (;) inserted between the two _withAsyncContext blocks.

What is actually happening?

What is actually happening? *

The ASI guard (`;`) is missing. 

Because of this, the JavaScript engine interprets the second statement as a function call invoked on the result of the first statement, causing a runtime error: `TypeError: (...) is not a function`.

([temp,restore] = _withAsyncContext(() => Promise.resolve(1))),
await __temp,
__restore()
)( // <--- RUNTIME ERROR
([temp,restore] = _withAsyncContext(() => Promise.resolve(2))),
await __temp,
__restore()
)


### System Info

System:
OS: Linux 5.10 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
CPU: (4) x64 AMD EPYC 9575F 64-Core Processor
Memory: 6.69 GB / 11.65 GB
Container: Yes
Shell: 5.1.4 - /bin/bash
Binaries:
Node: 24.14.1 - /root/.nvm/versions/node/v24.14.1/bin/node
Yarn: 1.22.22 - /root/.yarn/bin/yarn
npm: 11.11.0 - /root/.nvm/versions/node/v24.14.1/bin/npm
pnpm: 10.33.0 - /root/.nvm/versions/node/v24.14.1/bin/pnpm
Browsers:
Chrome: 150.0.7871.181
npmPackages:
vue: ^3.5.40 => 3.5.40


### Any additional comments?

**Root Cause:**
The bug is caused by a typo in the AST walker configuration inside `compiler-sfc`. The compiler uses `estree-walker` which expects the hooks `{ enter, leave }`. However, the code currently passes `{ enter, exit }`.

Since `exit` is not a valid hook in `estree-walker`, it is never called. Consequently, `scope.pop()` is never executed when leaving a `BlockStatement` (like the `if` block in the reproduction). This corrupts the `scope` stack, causing the `needsSemi` calculation to fail for all subsequent `AwaitExpression` nodes.

**Proposed Fix:**
Simply change `exit` to `leave` in the walker options:
  • exit(node2) {
  • leave(node2) { if (node2.type === "BlockStatement") scope.pop(); }

The two patches

Our patch+33 −1
packages/compiler-sfc/__tests__/compileScript.spec.tsindex d54541019..1e42b0966 100644@@ -1013,6 +1013,38 @@ describe('SFC compile <script setup>', () => {       }`)     }) +    // scope must be popped when leaving a nested block, otherwise+    // awaits following it are checked against the wrong block and lose their+    // leading semicolon (ASI guard), causing a runtime error+    test('consecutive awaits after a nested block', () => {+      const { content } = compile(`<script setup>if (ok) {+        if (a) {+          foo()+        }+        await 1+        await 2+      }</script>`)+      expect(content).toMatch(+        /__restore\(\)\n\)\n\s*;\(\n\s*\(\[__temp,__restore\] = _withAsyncContext\(\(\) => 2\)\)/,+      )+      expect(content).toMatch(+        /\}\n\s*;\(\n\s*\(\[__temp,__restore\] = _withAsyncContext\(\(\) => 1\)\)/,+      )+    })++    test('consecutive awaits after a nested loop block', () => {+      const { content } = compile(`<script setup>if (ok) {+        for (const i of list) {+          foo(i)+        }+        await 1+        await 2+      }</script>`)+      expect(content).toMatch(+        /__restore\(\)\n\)\n\s*;\(\n\s*\(\[__temp,__restore\] = _withAsyncContext\(\(\) => 2\)\)/,+      )+    })+     test('should ignore await inside functions', () => {       // function declaration       assertAwaitDetection(`async function foo() { await bar }`, false)packages/compiler-sfc/src/compileScript.tsindex d2047c5b2..901196235 100644@@ -669,7 +669,7 @@ export function compileScript(             )           }         },-        exit(node: Node) {+        leave(node: Node) {           if (node.type === 'BlockStatement') scope.pop()         },       }) 
Merged fix · PR #+20 −1
packages/compiler-sfc/__tests__/compileScript.spec.tsindex d54541019..a1cc885cd 100644@@ -1026,6 +1026,25 @@ describe('SFC compile <script setup>', () => {         false,       )     })++    // #15465+    test('await statements after a nested block should be separated', async () => {+      const { content } = compile(+        `<script setup>+        if (true) {+          if (false) {}+          await Promise.resolve(1)+          await Promise.resolve(2)+        }+        </script>`,+        { genDefaultAs: '_sfc_' },+      )+      const component = new Function(+        '_withAsyncContext',+        `${content.replace(/^import .*\n/, '')};return _sfc_`,+      )((getAwaitable: () => unknown) => [getAwaitable(), () => {}])+      await expect(component.setup({}, { expose() {} })).resolves.toEqual({})+    })   })    describe('errors', () => {packages/compiler-sfc/src/compileScript.tsindex d2047c5b2..901196235 100644@@ -669,7 +669,7 @@ export function compileScript(             )           }         },-        exit(node: Node) {+        leave(node: Node) {           if (node.type === 'BlockStatement') scope.pop()         },       })