Turbopack Error: Failed to write app endpoint /page

[rakibal123]

Turbopack version: 0c06f068
Next.js version: 0.0.0

Error message:

Failed to write app endpoint /page

Caused by:
- Next.js package not found

Debug info:
- Execution of Project::hmr_version_state failed
- Execution of Project::hmr_version failed
- Execution of VersionedContentMap::get failed
- Execution of VersionedContentMap::get_asset failed
- Execution of VersionedContentMap::compute_entry failed
- Execution of *emit_assets failed
- Execution of all_assets_from_entries_operation failed
- Execution of *all_assets_from_entries failed
- Execution of endpoint_output_assets_operation failed
- Execution of <AppEndpoint as Endpoint>::output failed
- Failed to write app endpoint /page
- Execution of AppEndpoint::output failed
- Execution of AppEndpoint::app_page_entry failed
- Execution of *get_app_page_entry failed
- Execution of AppProject::rsc_module_context failed
- Execution of *ModuleAssetContext::new failed
- Execution of *AppProject::get_rsc_transitions failed
- Execution of AppProject::ecmascript_client_reference_transition failed
- Execution of *NextEcmascriptClientReferenceTransition::new failed
- Execution of AppProject::ssr_transition failed
- Execution of *FullContextTransition::new failed
- Execution of AppProject::ssr_module_context failed
- Execution of AppProject::shared_transition failed
- Execution of *FullContextTransition::new failed
- Execution of AppProject::shared_module_context failed
- Execution of *ModuleAssetContext::new failed
- Execution of get_server_resolve_options_context failed
- Execution of get_next_server_import_map failed
- Next.js package not found

[pratikrath126]

The error usually means Turbopack can't resolve the package from your project. Common fixes:

1. Ensure is listed in your dependencies (not just devDependencies) and is installed. Try
   added 22 packages, and audited 39 packages in 26s

7 packages are looking for funding
run npm fund for details

found 0 vulnerabilities or .
2. Clear Turbopack cache: delete and (or ), then rebuild.
3. Verify you are using a compatible Next.js version with your Turbopack (canary builds may need matching versions). If using Next.js canary, ensure you're on the latest commit.
4. Check that your doesn't have custom webpack/turbopack config that interferes with package resolution.
5. If using pnpm, ensure proper linking; try or set in .

If the issue persists, consider filing an issue with a minimal reproduction.