Process completed with exit code 1.

Error: Command "pnpm build" failed with exit code 1 > nextjs-webpack@0.0.2-alpha.5 prebuild /tmp/workflow-nextjs-webpack-bDvodc/workbench/nextjs-webpack > pnpm generate:workflows > nextjs-webpack@0.0.2-alpha.5 generate:workflows /tmp/workflow-nextjs-webpack-bDvodc/workbench/nextjs-webpack > node ../scripts/generate-workflows-registry.js ✓ Generated ./_workflows.ts with 15 workflow(s) - workflows/100_durable_agent_e2e.ts - workflows/10_single_stmt_control_flow.ts - workflows/1_simple.ts - workflows/2_control_flow.ts - workflows/3_streams.ts - workflows/4_ai.ts - workflows/5_hooks.ts - workflows/6_batching.ts - workflows/7_full.ts - workflows/8_react_render.tsx - workflows/98_duplicate_case.ts - workflows/99_e2e.ts - workflows/agent_chat.ts - workflows/serde-models.ts - workflows/serde-steps.ts > nextjs-webpack@0.0.2-alpha.5 build /tmp/workflow-nextjs-webpack-bDvodc/workbench/nextjs-webpack > next build --webpack Attention: Next.js now collects completely anonymous telemetry regarding usage. This information is used to shape Next.js' roadmap and prioritize features. You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: https://nextjs.org/telemetry ▲ Next.js 16.2.1 (webpack) - Experiments (use with caution): · deferredEntries · onBeforeDeferredEntries ⨯ serverMinification Creating an optimized production build ... Failed to compile. ./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node Module parse failed: Unexpected character '�' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) Import trace for requested module: ./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node ./node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js ./node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js ./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js ./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js ./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index.js ./node_modules/.pnpm/@vercel+queue@0.1.4/node_modules/@vercel/queue/dist/index.mjs ./node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/queue.js ./node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/index.js ./node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/world.js ./node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime.js ./node_modules/.pnpm/workflow@file+..+..+tarballs+workflow-5.0.0-beta.2.tgz_@nestjs+common@11.1.19_reflect-m_b69e931b2c51a2a5cba5d083f6730fe9/node_modules/workflow/dist/runtime.js ./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node Module parse failed: Unexpected character '�' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) Import trace for requested module: ./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node ./node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js ./node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modu

Process completed with exit code 1.

Error: Command "pnpm build" failed with exit code 1 > nextjs-turbopack@0.0.2-alpha.5 prebuild /tmp/workflow-nextjs-turbopack-svfvKc/workbench/nextjs-turbopack > pnpm generate:workflows > nextjs-turbopack@0.0.2-alpha.5 generate:workflows /tmp/workflow-nextjs-turbopack-svfvKc/workbench/nextjs-turbopack > node ../scripts/generate-workflows-registry.js ✓ Generated ./_workflows.ts with 19 workflow(s) - workflows/100_durable_agent_e2e.ts - workflows/10_single_stmt_control_flow.ts - workflows/1_simple.ts - workflows/2_control_flow.ts - workflows/3_streams.ts - workflows/4_ai.ts - workflows/5_hooks.ts - workflows/6_batching.ts - workflows/7_full.ts - workflows/8_react_render.tsx - workflows/96_many_steps.ts - workflows/97_bench.ts - workflows/98_duplicate_case.ts - workflows/99_e2e.ts - workflows/agent_chat.ts - workflows/serde-models.ts - workflows/serde-steps.ts - workflows/server_action_step_import_helpers.ts - workflows/server_action_step_imports.ts > nextjs-turbopack@0.0.2-alpha.5 build /tmp/workflow-nextjs-turbopack-svfvKc/workbench/nextjs-turbopack > next build --turbopack Attention: Next.js now collects completely anonymous telemetry regarding usage. This information is used to shape Next.js' roadmap and prioritize features. You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: https://nextjs.org/telemetry ▲ Next.js 16.2.1 (Turbopack) - Experiments (use with caution): · deferredEntries · onBeforeDeferredEntries Creating an optimized production build ... > Build error occurred Error: Turbopack build failed with 2 errors: ./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js non-ecmascript placeable asset asset is not placeable in ESM chunks, so it doesn't have a module id Import traces: App Route: ./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+queue@0.1.4/node_modules/@vercel/queue/dist/index.mjs ./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/queue.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/index.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/world.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/run.js ./workbench/nextjs-turbopack/app/api/chat/[runId]/stream/route.ts Instrumentation: ./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index

Process completed with exit code 1.

Error: Command "pnpm build" failed with exit code 1 > nextjs-webpack@0.0.2-alpha.5 prebuild /tmp/workflow-nextjs-webpack-1qwphR/workbench/nextjs-webpack > pnpm generate:workflows > nextjs-webpack@0.0.2-alpha.5 generate:workflows /tmp/workflow-nextjs-webpack-1qwphR/workbench/nextjs-webpack > node ../scripts/generate-workflows-registry.js ✓ Generated ./_workflows.ts with 15 workflow(s) - workflows/100_durable_agent_e2e.ts - workflows/10_single_stmt_control_flow.ts - workflows/1_simple.ts - workflows/2_control_flow.ts - workflows/3_streams.ts - workflows/4_ai.ts - workflows/5_hooks.ts - workflows/6_batching.ts - workflows/7_full.ts - workflows/8_react_render.tsx - workflows/98_duplicate_case.ts - workflows/99_e2e.ts - workflows/agent_chat.ts - workflows/serde-models.ts - workflows/serde-steps.ts > nextjs-webpack@0.0.2-alpha.5 build /tmp/workflow-nextjs-webpack-1qwphR/workbench/nextjs-webpack > next build --webpack Attention: Next.js now collects completely anonymous telemetry regarding usage. This information is used to shape Next.js' roadmap and prioritize features. You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: https://nextjs.org/telemetry ▲ Next.js 16.2.1 (webpack) - Experiments (use with caution): · deferredEntries · onBeforeDeferredEntries ⨯ serverMinification Creating an optimized production build ... Failed to compile. ./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node Module parse failed: Unexpected character '�' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) Import trace for requested module: ./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node ./node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js ./node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js ./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js ./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js ./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index.js ./node_modules/.pnpm/@vercel+queue@0.1.4/node_modules/@vercel/queue/dist/index.mjs ./node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/queue.js ./node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/index.js ./node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/world.js ./node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime.js ./node_modules/.pnpm/workflow@file+..+..+tarballs+workflow-5.0.0-beta.2.tgz_@nestjs+common@11.1.19_reflect-m_b69e931b2c51a2a5cba5d083f6730fe9/node_modules/workflow/dist/runtime.js ./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node Module parse failed: Unexpected character '�' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) Import trace for requested module: ./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node ./node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js ./node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modu

Process completed with exit code 1.

Error: Command "pnpm build" failed with exit code 1 > nextjs-turbopack@0.0.2-alpha.5 prebuild /tmp/workflow-nextjs-turbopack-GC5kgZ/workbench/nextjs-turbopack > pnpm generate:workflows > nextjs-turbopack@0.0.2-alpha.5 generate:workflows /tmp/workflow-nextjs-turbopack-GC5kgZ/workbench/nextjs-turbopack > node ../scripts/generate-workflows-registry.js ✓ Generated ./_workflows.ts with 19 workflow(s) - workflows/100_durable_agent_e2e.ts - workflows/10_single_stmt_control_flow.ts - workflows/1_simple.ts - workflows/2_control_flow.ts - workflows/3_streams.ts - workflows/4_ai.ts - workflows/5_hooks.ts - workflows/6_batching.ts - workflows/7_full.ts - workflows/8_react_render.tsx - workflows/96_many_steps.ts - workflows/97_bench.ts - workflows/98_duplicate_case.ts - workflows/99_e2e.ts - workflows/agent_chat.ts - workflows/serde-models.ts - workflows/serde-steps.ts - workflows/server_action_step_import_helpers.ts - workflows/server_action_step_imports.ts > nextjs-turbopack@0.0.2-alpha.5 build /tmp/workflow-nextjs-turbopack-GC5kgZ/workbench/nextjs-turbopack > next build --turbopack Attention: Next.js now collects completely anonymous telemetry regarding usage. This information is used to shape Next.js' roadmap and prioritize features. You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: https://nextjs.org/telemetry ▲ Next.js 16.3.0-canary.2 (Turbopack) - Experiments (use with caution): · deferredEntries · onBeforeDeferredEntries Creating an optimized production build ... > Build error occurred Error: Turbopack build failed with 2 errors: ./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js non-ecmascript placeable asset asset is not placeable in ESM chunks, so it doesn't have a module id Import traces: App Route: ./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+queue@0.1.4/node_modules/@vercel/queue/dist/index.mjs ./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/queue.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/index.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/world.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/run.js ./workbench/nextjs-turbopack/app/api/chat/[runId]/stream/route.ts Instrumentation: ./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/d

Process completed with exit code 1.

Error: Command "pnpm build" failed with exit code 1 > nextjs-turbopack@0.0.2-alpha.5 prebuild /tmp/workflow-nextjs-turbopack-vI5RMa/workbench/nextjs-turbopack > pnpm generate:workflows > nextjs-turbopack@0.0.2-alpha.5 generate:workflows /tmp/workflow-nextjs-turbopack-vI5RMa/workbench/nextjs-turbopack > node ../scripts/generate-workflows-registry.js ✓ Generated ./_workflows.ts with 19 workflow(s) - workflows/100_durable_agent_e2e.ts - workflows/10_single_stmt_control_flow.ts - workflows/1_simple.ts - workflows/2_control_flow.ts - workflows/3_streams.ts - workflows/4_ai.ts - workflows/5_hooks.ts - workflows/6_batching.ts - workflows/7_full.ts - workflows/8_react_render.tsx - workflows/96_many_steps.ts - workflows/97_bench.ts - workflows/98_duplicate_case.ts - workflows/99_e2e.ts - workflows/agent_chat.ts - workflows/serde-models.ts - workflows/serde-steps.ts - workflows/server_action_step_import_helpers.ts - workflows/server_action_step_imports.ts > nextjs-turbopack@0.0.2-alpha.5 build /tmp/workflow-nextjs-turbopack-vI5RMa/workbench/nextjs-turbopack > next build --turbopack Attention: Next.js now collects completely anonymous telemetry regarding usage. This information is used to shape Next.js' roadmap and prioritize features. You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: https://nextjs.org/telemetry ▲ Next.js 16.2.1 (Turbopack) - Experiments (use with caution): · deferredEntries · onBeforeDeferredEntries Creating an optimized production build ... > Build error occurred Error: Turbopack build failed with 2 errors: ./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js non-ecmascript placeable asset asset is not placeable in ESM chunks, so it doesn't have a module id Import traces: App Route: ./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+queue@0.1.4/node_modules/@vercel/queue/dist/index.mjs ./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/queue.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/index.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/world.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/run.js ./workbench/nextjs-turbopack/app/api/chat/[runId]/stream/route.ts Instrumentation: ./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index

Process completed with exit code 1.

Error: Command "pnpm build" failed with exit code 1 > nextjs-webpack@0.0.2-alpha.5 prebuild /tmp/workflow-nextjs-webpack-Os7GwX/workbench/nextjs-webpack > pnpm generate:workflows > nextjs-webpack@0.0.2-alpha.5 generate:workflows /tmp/workflow-nextjs-webpack-Os7GwX/workbench/nextjs-webpack > node ../scripts/generate-workflows-registry.js ✓ Generated ./_workflows.ts with 15 workflow(s) - workflows/100_durable_agent_e2e.ts - workflows/10_single_stmt_control_flow.ts - workflows/1_simple.ts - workflows/2_control_flow.ts - workflows/3_streams.ts - workflows/4_ai.ts - workflows/5_hooks.ts - workflows/6_batching.ts - workflows/7_full.ts - workflows/8_react_render.tsx - workflows/98_duplicate_case.ts - workflows/99_e2e.ts - workflows/agent_chat.ts - workflows/serde-models.ts - workflows/serde-steps.ts > nextjs-webpack@0.0.2-alpha.5 build /tmp/workflow-nextjs-webpack-Os7GwX/workbench/nextjs-webpack > next build --webpack Attention: Next.js now collects completely anonymous telemetry regarding usage. This information is used to shape Next.js' roadmap and prioritize features. You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: https://nextjs.org/telemetry ▲ Next.js 16.3.0-canary.2 (webpack) - Experiments (use with caution): · deferredEntries · onBeforeDeferredEntries ⨯ serverMinification Creating an optimized production build ... Failed to compile. ./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node Module parse failed: Unexpected character '�' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) Import trace for requested module: ./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node ./node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js ./node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js ./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js ./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js ./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/get-vercel-oidc-token.js ./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index.js ./node_modules/.pnpm/@vercel+queue@0.1.4/node_modules/@vercel/queue/dist/index.mjs ./node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/queue.js ./node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/index.js ./node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/world.js ./node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime.js ./node_modules/.pnpm/workflow@file+..+..+tarballs+workflow-5.0.0-beta.2.tgz_@nestjs+common@11.1.19_reflect-m_4c42f3f5f9f5fc457ff30c948191b6a5/node_modules/workflow/dist/runtime.js ./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node Module parse failed: Unexpected character '�' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) Import trace for requested module: ./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node ./node_modules/.pnpm/@napi-rs+k

Process completed with exit code 1.

Error: Command "pnpm build" failed with exit code 1 > nextjs-turbopack@0.0.2-alpha.5 prebuild /tmp/workflow-nextjs-turbopack-M6Vxs9/workbench/nextjs-turbopack > pnpm generate:workflows > nextjs-turbopack@0.0.2-alpha.5 generate:workflows /tmp/workflow-nextjs-turbopack-M6Vxs9/workbench/nextjs-turbopack > node ../scripts/generate-workflows-registry.js ✓ Generated ./_workflows.ts with 19 workflow(s) - workflows/100_durable_agent_e2e.ts - workflows/10_single_stmt_control_flow.ts - workflows/1_simple.ts - workflows/2_control_flow.ts - workflows/3_streams.ts - workflows/4_ai.ts - workflows/5_hooks.ts - workflows/6_batching.ts - workflows/7_full.ts - workflows/8_react_render.tsx - workflows/96_many_steps.ts - workflows/97_bench.ts - workflows/98_duplicate_case.ts - workflows/99_e2e.ts - workflows/agent_chat.ts - workflows/serde-models.ts - workflows/serde-steps.ts - workflows/server_action_step_import_helpers.ts - workflows/server_action_step_imports.ts > nextjs-turbopack@0.0.2-alpha.5 build /tmp/workflow-nextjs-turbopack-M6Vxs9/workbench/nextjs-turbopack > next build --turbopack Attention: Next.js now collects completely anonymous telemetry regarding usage. This information is used to shape Next.js' roadmap and prioritize features. You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: https://nextjs.org/telemetry ▲ Next.js 16.3.0-canary.2 (Turbopack) - Experiments (use with caution): · deferredEntries · onBeforeDeferredEntries Creating an optimized production build ... > Build error occurred Error: Turbopack build failed with 2 errors: ./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js non-ecmascript placeable asset asset is not placeable in ESM chunks, so it doesn't have a module id Import traces: App Route: ./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+queue@0.1.4/node_modules/@vercel/queue/dist/index.mjs ./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/queue.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/index.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/world.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/run.js ./workbench/nextjs-turbopack/app/api/chat/[runId]/stream/route.ts Instrumentation: ./workbench/nextjs-turbopack/node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js ./workbench/nextjs-turbopack/node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/d

Process completed with exit code 1.

Error: Command "pnpm build" failed with exit code 1 > nextjs-webpack@0.0.2-alpha.5 prebuild /tmp/workflow-nextjs-webpack-7qqcer/workbench/nextjs-webpack > pnpm generate:workflows > nextjs-webpack@0.0.2-alpha.5 generate:workflows /tmp/workflow-nextjs-webpack-7qqcer/workbench/nextjs-webpack > node ../scripts/generate-workflows-registry.js ✓ Generated ./_workflows.ts with 15 workflow(s) - workflows/100_durable_agent_e2e.ts - workflows/10_single_stmt_control_flow.ts - workflows/1_simple.ts - workflows/2_control_flow.ts - workflows/3_streams.ts - workflows/4_ai.ts - workflows/5_hooks.ts - workflows/6_batching.ts - workflows/7_full.ts - workflows/8_react_render.tsx - workflows/98_duplicate_case.ts - workflows/99_e2e.ts - workflows/agent_chat.ts - workflows/serde-models.ts - workflows/serde-steps.ts > nextjs-webpack@0.0.2-alpha.5 build /tmp/workflow-nextjs-webpack-7qqcer/workbench/nextjs-webpack > next build --webpack Attention: Next.js now collects completely anonymous telemetry regarding usage. This information is used to shape Next.js' roadmap and prioritize features. You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: https://nextjs.org/telemetry ▲ Next.js 16.3.0-canary.2 (webpack) - Experiments (use with caution): · deferredEntries · onBeforeDeferredEntries ⨯ serverMinification Creating an optimized production build ... Failed to compile. ./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node Module parse failed: Unexpected character '�' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) Import trace for requested module: ./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node ./node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js ./node_modules/.pnpm/@vercel+cli-auth@0.1.0/node_modules/@vercel/cli-auth/credentials-store.js ./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/auth-config.js ./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/token-util.js ./node_modules/.pnpm/@vercel+oidc@3.3.0/node_modules/@vercel/oidc/dist/index.js ./node_modules/.pnpm/@vercel+queue@0.1.4/node_modules/@vercel/queue/dist/index.mjs ./node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/queue.js ./node_modules/.pnpm/@workflow+world-vercel@file+..+..+tarballs+workflow-world-vercel-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/world-vercel/dist/index.js ./node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime/world.js ./node_modules/.pnpm/@workflow+core@file+..+..+tarballs+workflow-core-5.0.0-beta.2.tgz_@opentelemetry+api@1.9.1/node_modules/@workflow/core/dist/runtime.js ./node_modules/.pnpm/workflow@file+..+..+tarballs+workflow-5.0.0-beta.2.tgz_@nestjs+common@11.1.19_reflect-m_4c42f3f5f9f5fc457ff30c948191b6a5/node_modules/workflow/dist/runtime.js ./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node Module parse failed: Unexpected character '�' (1:0) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders (Source code omitted for this binary file) Import trace for requested module: ./node_modules/.pnpm/@napi-rs+keyring-linux-x64-gnu@1.2.0/node_modules/@napi-rs/keyring-linux-x64-gnu/keyring.linux-x64-gnu.node ./node_modules/.pnpm/@napi-rs+keyring@1.2.0/node_modules/@napi-rs/keyring/index.js ./node_modules/.pnpm/@vercel+cli-auth@0.1.0/

Process completed with exit code 1.

Error: Timed out after 50000ms waiting for manifest.json to include imported step hot-reload marker. Last error: Failed to trigger workflow "importedStepOnlyWorkflow": 500 ❯ pollUntil packages/core/e2e/dev.test.ts:143:13 ❯ packages/core/e2e/dev.test.ts:254:9

Process completed with exit code 1.

Error: Timed out after 50000ms waiting for manifest.json to include imported step hot-reload marker. Last error: The operation was aborted due to timeout ❯ pollUntil packages/core/e2e/dev.test.ts:143:13 ❯ packages/core/e2e/dev.test.ts:254:9

Process completed with exit code 1.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/