nextjs - 💡(How to fix) Fix Turbopack Build Fails When Using Sanity CMS [2 comments, 3 participants]

next build --turbopack

▲ Next.js 15.5.4 (Turbopack)

• Environments: .env.local

Creating an optimized production build ...

thread 'tokio-runtime-worker' panicked at turbopack\crates\turbopack-ecmascript\src\lib.rs:2429:13: The high bits of the position 4218194 are not all 0s or 1s. modules_header_width=10, module=601 note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

thread 'tokio-runtime-worker' panicked at turbopack\crates\turbopack-ecmascript\src\lib.rs:2429:13: The high bits of the position 4218194 are not all 0s or 1s. modules_header_width=10, module=546 ✓ Finished writing to disk in 55ms

Build error occurred [Error: Turbopack build failed with 2 errors: ./node_modules/.pnpm/[email protected]_@emotion+is-p_b145ba7fae607919b1a73627c10e5b0e/node_modules/sanity/lib/index.mjs Code generation for chunk item errored An error occurred while generating the chunk item [project]/node_modules/.pnpm/[email protected]_@emotion+is-p_b145ba7fae607919b1a73627c10e5b0e/node_modules/sanity/lib/index.mjs [app-client] (ecmascript) <locals>

Caused by:

• The high bits of the position 4218194 are not all 0s or 1s. modules_header_width=10, module=601

Debug info:

• An error occurred while generating the chunk item [project]/node_modules/.pnpm/[email protected]_@emotion+is-p_b145ba7fae607919b1a73627c10e5b0e/node_modules/sanity/lib/index.mjs [app-client] (ecmascript) <locals>
• Execution of *EcmascriptChunkItemContent::module_factory failed
• Execution of <MergedEcmascriptModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
• Execution of *EcmascriptChunkItemContent::new failed
• Execution of EcmascriptModuleContent::new_merged failed
• The high bits of the position 4218194 are not all 0s or 1s. modules_header_width=10, module=601

./node_modules/.pnpm/[email protected]_@emotion+is-p_b145ba7fae607919b1a73627c10e5b0e/node_modules/sanity/lib/index.mjs Code generation for chunk item errored An error occurred while generating the chunk item [project]/node_modules/.pnpm/[email protected]_@emotion+is-p_b145ba7fae607919b1a73627c10e5b0e/node_modules/sanity/lib/index.mjs [app-ssr] (ecmascript) <locals>

Caused by:

• The high bits of the position 4218194 are not all 0s or 1s. modules_header_width=10, module=546

Debug info:

• An error occurred while generating the chunk item [project]/node_modules/.pnpm/[email protected]_@emotion+is-p_b145ba7fae607919b1a73627c10e5b0e/node_modules/sanity/lib/index.mjs [app-ssr] (ecmascript) <locals>
• Execution of *EcmascriptChunkItemContent::module_factory failed
• Execution of <MergedEcmascriptModuleChunkItem as EcmascriptChunkItem>::content_with_async_module_info failed
• Execution of *EcmascriptChunkItemContent::new failed
• Execution of EcmascriptModuleContent::new_merged failed
• The high bits of the position 4218194 are not all 0s or 1s. modules_header_width=10, module=546

]  ELIFECYCLE  Command failed with exit code 1.

TL;DR

The issue is likely related to a compatibility problem between Next.js 15.5.4 and the Turbopack build process, specifically with the Sanity CMS module, and can be mitigated by adjusting the build configuration or updating dependencies.

Guidance

1. Check for updates: Ensure all dependencies, including Next.js and Sanity CMS, are up-to-date, as newer versions may resolve compatibility issues.
2. Adjust Turbopack configuration: Investigate if there are any configuration options for Turbopack that can help mitigate the issue, such as adjusting the modules_header_width.
3. Disable Turbopack for build: Temporarily disable Turbopack for the build process to see if the issue persists, by running next build without the --turbopack flag.
4. Test with different Node versions: Given the difference in Node versions between local and CI environments, test the build process with the same Node version used in the CI environment (Node 22.19.0) to isolate if the issue is Node version-specific.

Example

No specific code example is provided as the issue seems to be related to configuration and compatibility rather than a code snippet.

Notes

The solution may depend on the specific versions of Next.js, Turbopack, and Sanity CMS used. The issue appears in both local and CI environments, suggesting a deeper compatibility issue rather than an environment-specific problem.

Recommendation

Apply a workaround by disabling Turbopack for the build process or adjusting its configuration, as updating to a fixed version is not explicitly implied in the given information. This approach allows for temporary mitigation of the issue while awaiting further updates or fixes from the dependencies involved.