Turbopack Error: Failed to write app endpoint /page

[kanhadewangan]

Turbopack version: 9b25f18e
Next.js version: 0.0.0

Error message:

Failed to write app endpoint /page

Caused by:
- [project]/app/globals.css [app-client] (css)
- failed to deserialize message
- invalid type: null, expected a string

Debug info:
- Execution of get_written_endpoint_with_issues_operation failed
- Execution of endpoint_write_to_disk failed
- Execution of <AppEndpoint as Endpoint>::output failed
- Failed to write app endpoint /page
- Execution of AppEndpoint::output failed
- Execution of AppProject::app_module_graphs failed
- Execution of *<AppEndpoint as Endpoint>::additional_entries failed
- Execution of *ModuleGraph::from_graphs failed
- Execution of SingleModuleGraph::new_with_entries_visited_intern failed
- [project]/app/globals.css [app-client] (css)
- Execution of primary_chunkable_referenced_modules failed
- Execution of <CssModuleAsset as Module>::references failed
- Execution of parse_css failed
- Execution of <PostCssTransformedAsset as Asset>::content failed
- Execution of PostCssTransformedAsset::process failed
- failed to deserialize message
- invalid type: null, expected a string
    at .
         | v
       1 + {"type":"error","name":"Error","message":"It looks like you're trying to use `tailwindcss` directl...:null,"methodName":"processTicksAndRejections","arguments":["native"],"lineNumber":7,"column":39}]}
         | ^

[khasanbayev-7]

This error is related to Turbopack’s CSS asset deserialization during build — not a problem with your globals.css or Tailwind configuration itself.

---

🧩 What’s happening

In this stack trace:
failed to deserialize message
invalid type: null, expected a string

csharp
Копировать код
Turbopack is trying to parse a message object from its internal CSS transformation pipeline (involving PostCSS + TailwindCSS).
However, one of the expected string fields is null, which triggers the deserialization panic.

This bug occurs mostly in certain canary or internal Turbopack builds (for example 9b25f18e) and affects projects using global CSS imports under the app/ directory.

---

✅ Temporary Workarounds

1. Disable Turbopack (use Webpack temporarily)

   // next.config.js
   const nextConfig = {
     experimental: {
       turbo: false,
     },
   };
   module.exports = nextConfig;

Then run:

bash
Копировать код
npm run dev
This lets you continue development while Turbopack’s deserializer issue is being fixed upstream.

Ensure your Tailwind and PostCSS setup is standard
Check that your postcss.config.js and tailwind.config.js are at the project root and properly configured:

js
Копировать код
// postcss.config.js
module.exports = {
plugins: {
tailwindcss: {},
autoprefixer: {},
},
};
Clear your .next cache

bash
Копировать код
rm -rf .next
npm run dev
(Sometimes old serialized build artifacts trigger this null-type error.)

Downgrade to a stable Next.js version

bash
Копировать код
npm install next@15
Canary builds often include experimental serialization logic changes that may not be backward-compatible.

[kanhadewangan]

i try this , thank you for your help