Skip to content

fix(nextjs): handle process.turbopack is not supported in edge runtime #17574

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 6 commits into from
Closed

fix(nextjs): handle process.turbopack is not supported in edge runtime #17574

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
3332576
fix: `process.turbopack` is not supported in edge runtime
asionesjia Sep 9, 2025
dd0e8eb
fix(nextjs): replace unsupported `process.turbopack` with `process.en…
asionesjia Sep 9, 2025
0e8fc83
fix(nextjs): safely detect Turbopack in Edge/Browser environments
asionesjia Sep 9, 2025
579b737
Merge branch 'develop' into fix/process-turbopack-not-supported-in-ed…
asionesjia Sep 9, 2025
faffeb4
Merge branch 'develop' into fix/process-turbopack-not-supported-in-ed…
asionesjia Sep 10, 2025
3a13e0e
fix(nextjs): simplify Turbopack detection using process.env.TURBOPACK
asionesjia Sep 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions packages/nextjs/src/client/index.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,8 +77,7 @@ export function init(options: BrowserOptions): Client | undefined {
}

try {
// @ts-expect-error `process.turbopack` is a magic string that will be replaced by Next.js
if (process.turbopack) {
if (process.env.TURBOPACK) {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Turbopack Detection Regression

Replacing process.turbopack with process.env.TURBOPACK breaks Next.js's build-time magic string replacement for Turbopack detection. This implementation also doesn't align with the PR description, which proposed a fallback checking both process.env.TURBOPACK and process.turbopack to ensure detection works as expected.

Additional Locations (2)

Fix in Cursor Fix in Web

getGlobalScope().setTag('turbopack', true);
}
} catch {
Expand Down
3 changes: 1 addition & 2 deletions packages/nextjs/src/edge/index.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,8 +95,7 @@ export function init(options: VercelEdgeOptions = {}): void {
});

try {
// @ts-expect-error `process.turbopack` is a magic string that will be replaced by Next.js
if (process.turbopack) {
if (process.env.TURBOPACK) {
getGlobalScope().setTag('turbopack', true);
}
} catch {
Expand Down
3 changes: 1 addition & 2 deletions packages/nextjs/src/server/index.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -368,8 +368,7 @@ export function init(options: NodeOptions): NodeClient | undefined {
}

try {
// @ts-expect-error `process.turbopack` is a magic string that will be replaced by Next.js
if (process.turbopack) {
if (process.env.TURBOPACK) {
getGlobalScope().setTag('turbopack', true);
}
} catch {
Expand Down