Turbopack Error: failed to analyse ecmascript module '[project]/middleware.ts [middleware-edge] (ecmascript)'

[Xevrrer]

Turbopack version: b2d6b361
Next.js version: 15.4.0-canary.95, 15.4.0-canary.96 and 15.4.0-canary.97
OS: Windows 11
Package manager: PNPM 10.12.2
Node Version: 22.17.0

On 15.4.0-canary.94 and before everything working correctly

Error message after type pnpm dev (next dev --turbopack)

failed to analyse ecmascript module '[project]/middleware.ts [middleware-edge] (ecmascript)'

Caused by:
- failed to parse [project]/middleware.ts
- Transforming and/or parsing of [project]/middleware.ts failed
- Node.js version parse error

Debug info:
- Execution of get_entrypoints_with_issues_operation failed
- Execution of EntrypointsOperation::new failed
- Execution of Project::entrypoints failed
- Execution of Project::middleware_endpoint failed
- Execution of *MiddlewareEndpoint::new failed
- Execution of Project::middleware_context failed
- Execution of *parse_config_from_source failed
- Execution of *ProcessResult::module failed
- Execution of apply_module_type failed
- Execution of *EcmascriptExports::needs_facade failed
- Execution of <EcmascriptModuleAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/middleware.ts [middleware-edge] (ecmascript)'
- Execution of <EcmascriptModuleAsset as EcmascriptParsable>::failsafe_parse failed
- Execution of parse failed
- failed to parse [project]/middleware.ts
- Transforming and/or parsing of [project]/middleware.ts failed
- Execution of EdgeWorkerEnvironment::runtime_versions failed
- Node.js version parse error]

middleware.ts

import { NextResponse } from "next/server";
//import redis from '@/lib/redis';

import type { NextRequest } from "next/server";

export async function middleware(request: NextRequest): Promise<NextResponse> {
	if (request.method === "GET") {
		const response = NextResponse.next();
		const token = request.cookies.get("session")?.value ?? null;
		if (token !== null) {
			response.cookies.set("session", token, {
				path: "/",
				maxAge: 60 * 60 * 24 * 30,
				sameSite: "lax",
				httpOnly: true,
				secure: process.env.NODE_ENV === "production"
			});
		}
		return response;
	}


	return NextResponse.next();
}

removing middleware.ts solve this problem.

[Xevrrer]

The error still exists on 15.4.0-canary.97.

The problem doesn't lie in the middleware itself—after removing it, I now see that I can't access any pages at all. Every subpage returns an Internal Server Error along with the similar error as in the first post.

Debug info:
- Execution of TaskId { id: 2147483661 } transient failed
- Execution of get_written_endpoint_with_issues_operation failed
- Execution of endpoint_write_to_disk failed
- Execution of <PageEndpoint as Endpoint>::output failed
- Failed to write page endpoint /_app
- Execution of PageEndpoint::output failed
- Execution of PageEndpoint::internal_ssr_chunk failed
- Execution of PageEndpoint::internal_ssr_chunk_module failed
- Execution of *parse_config_from_source failed
- Execution of *ProcessResult::module failed
- Execution of apply_module_type failed
- Execution of *EcmascriptExports::needs_facade failed
- Execution of <EcmascriptModuleAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyse_ecmascript_module failed
- failed to analyse ecmascript module '[project]/node_modules/.pnpm/next@15.4.0-canary.97_@babe_0935ff08ba2c4a0f3df3457bf9e68326/node_modules/next/app.js [ssr] (ecmascript)'
- Execution of <EcmascriptModuleAsset as EcmascriptParsable>::failsafe_parse failed
- Execution of parse failed
- failed to parse [project]/node_modules/.pnpm/next@15.4.0-canary.97_@babe_0935ff08ba2c4a0f3df3457bf9e68326/node_modules/next/app.js
- Transforming and/or parsing of [project]/node_modules/.pnpm/next@15.4.0-canary.97_@babe_0935ff08ba2c4a0f3df3457bf9e68326/node_modules/next/app.js failed
- Execution of NodeJsEnvironment::runtime_versions failed
- Node.js version parse error]

[icyJoseph]

Hi, thank you for this report, and the level of detail. Will be fixed by #80949