test: avoid Windows long-path failures in isolated Next.js installs #87197
+9
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Fix flakiness on Windows when tests create an isolated Next.js install under %TEMP%.
Long temp directory names can exceed Windows path limitations and cause Turbopack to fail resolving
next/package.json/ workspace root.How
Shorten the random suffix used for isolated temp dirs on Windows (keep existing behavior on non-Windows).
Why
This makes the new dev test(s) reliable on Windows for both Webpack and Turbopack.
Test Plan
test/development/pages-dir/http-methods/http-methods.test.ts