next.js
e1e25e16 - use server component transform for segment validation (#72051)

Commit
1 year ago
use server component transform for segment validation (#72051) After adding validation that fixing invalid segment configs (when DIO is enabled), it revealed that errors weren't being displayed in Turbopack, because `setHMRServerError` wasn't implemented. This refactors the implementation to use the existing server component transform when validating if the segments are valid. This has the benefit of highlighting precisely where the segment is coming, making it easier to remove. The test that was skipped in Turbopack is also re-enabled. <details> <summary>Screenshot</summary> ![CleanShot 2024-10-29 at 17 03 46@2x](https://github.com/user-attachments/assets/a68c060a-6ae7-4c6c-8243-6c48c2703f66) </details>
Author
Parents
Loading