cloudflare/vinext

Build failure: non-hoisted SWC helpers cause deploy script failure

Closed

#1,511 opened on May 22, 2026

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)TypeScript (371 forks)github user discovery
adapter-api-e2ehelp wanted

Repository metrics

Stars
 (8,563 stars)
PR merge metrics
 (Avg merge 1d 1h) (462 merged PRs in 30d)

Description

This issue was created by an agent analysing CI failures from the Next.js Deploy Suite (vinext main vs Next.js v16.2.6, 2026-05-22).

Problem

Test handle-non-hoisted-swc-helpers fails the entire build with Custom deploy script failed: undefined (1). The vinext build pipeline cannot handle code where SWC helpers (e.g. _inherits, _classCallCheck) end up non-hoisted in the bundled output.

Non-hoisted SWC helpers cause deploy script failure

Estimated Impact

~1 test failures across the deploy suite.

Affected Test Suites

  • test/e2e/handle-non-hoisted-swc-helpers/index.test.ts

Recommendation

  1. Reproduce first in vinext's own test suite. Add a page that uses class inheritance and ensure the SWC helpers are not hoisted to the top of the output bundle.

  2. Hoist helpers in the transform. Make sure helper declarations are emitted at the top of each chunk.

Part of #1328.

Contributor guide

Research direction
Reproduce the issue by adding a test page with class inheritance and trace where SWC helpers are placed in the bundle. Then adjust the transform to hoist helper declarations to the top of each chunk.
Tech stack
typescriptvitenodejs
Domain
build systemtooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70