We had to disable the --turbo flag in the development script due to an error when updating to Nextjs 14.2 (#6803). It would be good to re-enable it once the underlying issue is resolved.
Steps to Reproduce
- Enable the
--turbo flag in the dev script.
- Run the development server.
Error: Expected process result to be a module, but it was ignored
Debug info:
- Execution of get_written_endpoint_with_issues failed
- Execution of <AppEndpoint as Endpoint>::write_to_disk failed
- Execution of Project::emit_all_output_assets failed
- Execution of VersionedContentMap::insert_output_assets failed
- Execution of all_assets_from_entries failed
- Execution of AppEndpointOutput::output_assets failed
- Execution of AppEndpoint::output failed
- Execution of ClientReferenceGraph::entry failed
- Execution of ClientReferenceGraph::new failed
- Execution of primary_referenced_modules failed
- Execution of <ModuleCssAsset as Module>::references failed
- Execution of ModuleCssAsset::module_references failed
- Execution of ModuleCssAsset::classes failed
- Execution of process_css_with_placeholder failed
- Execution of parse_css failed
- Execution of <PostCssTransformedAsset as Asset>::content failed
- Execution of PostCssTransformedAsset::process failed
- Execution of evaluate_webpack_loader failed
- Execution of Completions::completed failed
- Execution of any_content_changed_of_module failed
- Execution of ProcessResult::module failed
- Expected process result to be a module, but it was ignored
Expected Behavior
The development server should run without errors with the --turbo flag enabled.
We had to disable the
--turboflag in the development script due to an error when updating to Nextjs 14.2 (#6803). It would be good to re-enable it once the underlying issue is resolved.Steps to Reproduce
--turboflag in the dev script.Expected Behavior
The development server should run without errors with the
--turboflag enabled.