Turbopack Error: Failed to write app endpoint /favicon.ico/route

[pan93412]

Turbopack version: v16.0.1-9-gc8f3be7e8
Next.js version: 16.0.2-canary.0

Error message:

Failed to write app endpoint /favicon.ico/route

Caused by:
- failed to analyze ecmascript module '[project]/app/favicon--route-entry.js [app-route] (ecmascript)'
- failed to parse [project]/app/favicon--route-entry.js
- Transforming and/or parsing of [project]/app/favicon--route-entry.js failed
- failed to run Wasm plugin transform. Please ensure the version of `swc_core` used by the plugin is compatible with the host runtime. See the documentation for compatibility information. If you are an author of the plugin, please update `swc_core` to the compatible version.
- Failed to deserialize program received from host

Debug info:
- Execution of get_all_written_entrypoints_with_issues_operation failed
- Execution of EntrypointsOperation::new failed
- Execution of all_entrypoints_write_to_disk_operation failed
- Execution of Project::emit_all_output_assets failed
- Execution of *emit_assets failed
- Execution of all_assets_from_entries_operation failed
- Execution of *all_assets_from_entries failed
- Execution of output_assets_operation failed
- Execution of <AppEndpoint as Endpoint>::output failed
- Failed to write app endpoint /favicon.ico/route
- Execution of AppEndpoint::output failed
- Execution of get_app_route_entry failed
- Execution of *ProcessResult::module failed
- Execution of <ModuleAssetContext as AssetContext>::process failed
- Execution of *EcmascriptExports::split_locals_and_reexports failed
- Execution of <EcmascriptModuleAsset as EcmascriptChunkPlaceable>::get_exports failed
- Execution of analyze_ecmascript_module failed
- failed to analyze ecmascript module '[project]/app/favicon--route-entry.js [app-route] (ecmascript)'
- Execution of parse failed
- failed to parse [project]/app/favicon--route-entry.js
- Transforming and/or parsing of [project]/app/favicon--route-entry.js failed
- failed to run Wasm plugin transform. Please ensure the version of `swc_core` used by the plugin is compatible with the host runtime. See the documentation for compatibility information. If you are an author of the plugin, please update `swc_core` to the compatible version.
  
                  Note that if you want to use the os features like filesystem, you need to use `wasi`. Wasm itself does not have concept of filesystem.
  
                  https://swc.rs/docs/plugin/selecting-swc-core
  
                  See https://plugins.swc.rs/versions/from-plugin-runner/20.0.0 for the list of the compatible versions.
  
                  Build info:
                      Date: 2025-10-28
                      Timestamp: 2025-10-28T21:26:40.392675000Z
  
                  Version info:
                      swc_plugin_runner: 20.0.0
                      Dependencies: anyhow 1.0.98,blake3 1.5.4,parking_lot 0.12.3,rustc-hash 2.1.1,serde 1.0.225,serde_json 1.0.140,swc_atoms 7.0.0,swc_common 15.0.0,swc_plugin_proxy 16.0.0,swc_transform_common 9.0.0,tracing 0.1.41,vergen 9.0.0
                  
- Failed to deserialize program received from host

Dependencies:

  [email protected](@babel/[email protected])(@opentelemetry/[email protected])([email protected])([email protected]([email protected]))([email protected]):
    dependencies:
      '@next/env': 16.0.2-canary.0
      '@swc/helpers': 0.5.15
      caniuse-lite: 1.0.30001751
      postcss: 8.4.31
      react: 19.3.0-canary-4f931700-20251029
      react-dom: 19.3.0-canary-4f931700-20251029([email protected])
      styled-jsx: 5.1.6(@babel/[email protected])([email protected])
    optionalDependencies:
      '@next/swc-darwin-arm64': 16.0.2-canary.0
      '@next/swc-darwin-x64': 16.0.2-canary.0
      '@next/swc-linux-arm64-gnu': 16.0.2-canary.0
      '@next/swc-linux-arm64-musl': 16.0.2-canary.0
      '@next/swc-linux-x64-gnu': 16.0.2-canary.0
      '@next/swc-linux-x64-musl': 16.0.2-canary.0
      '@next/swc-win32-arm64-msvc': 16.0.2-canary.0
      '@next/swc-win32-x64-msvc': 16.0.2-canary.0
      '@opentelemetry/api': 1.9.0
      babel-plugin-react-compiler: 19.1.0-rc.3
      sharp: 0.34.4
    transitivePeerDependencies:
      - '@babel/core'
      - babel-plugin-macros

[pan93412]

It seems that the issue is due to the dependency @swc-contrib/[email protected]. Locking it to 0.9.0 serves as a workaround.