Turbopack Error: Failed to write app endpoint /page

[IamHenryOkeke]

Turbopack version: db56d775
Next.js version: 0.0.0

Error message:

Failed to write app endpoint /page

Caused by:
- [project]/app/globals.css [app-client] (css)
- creating new process
- node process exited before we could connect to it with exit status: 127

Debug info:
- Execution of TaskId { id: 2147483652 } transient failed
- 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
- creating new process
- node process exited before we could connect to it with exit status: 127
  Process output:
  
  Process error output:
  /bin/sh: symbol lookup error: /home/nmesomahenry/.vscode/extensions/wallabyjs.console-ninja-1.0.483/out/console-ninja-fs-hooks.linux-x64-gnu.node: undefined symbol: napi_get_global

[Lochy2000]

The root cause is a symbol lookup error involving your Console Ninja VS Code extension. The error message is:

/bin/sh: symbol lookup error: .../wallabyjs.console-ninja-1.0.483/out/console-ninja-fs-hooks.linux-x64-gnu.node: undefined symbol: napi_get_global

This means a binary file used by that extension is incompatible with your current Node.js environment or operating system.

Possible solution:

• you could Disable or uninstall the Console Ninja extension. This instantly fixes the conflict and restores their ability to run next dev --turbo. This is the most crucial step.

• try updating ninja console extension in in your vs code

• It could be a nexjs, node and ninja mismatch depending on your versions, you could Try upgrading or downgrading local Node.js version to one that is known to work with the extension and Next.js.

hope this helps