fix(dev): use node pipelining on windows

[danielroe]

🔗 Linked issue

reported in nuxt/nuxt#33410 (comment) and on Discord

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

issue reproduced for files > ~131kB on windows on fetchable dev server.

this is only true when returning node streams - which was reproducible b/c nuxt/devtools was using sirv under the hood - also reproducible with ipx (<NuxtImg> was also mentioned)

at the point a file is > ~131kb we hit a deadlock, where no more can be written into the named pipe, and nothing can be cleared out of the socket

this fix skips using undici in this case in favour of using native node http

[github-actions]

📦 Bundle Size Comparison

📈 nuxi

Metric	Base	Head	Diff
Rendered	5074.46 KB	5076.47 KB	+2.01 KB (+0.04%)

📈 nuxt-cli

Metric	Base	Head	Diff
Rendered	104.21 KB	106.23 KB	+2.02 KB (+1.94%)

➡️ create-nuxt

Metric	Base	Head	Diff
Rendered	2178.73 KB	2178.73 KB	0.00 KB (0.00%)

[pkg-pr-new]

nuxt-cli-playground

npm i https://pkg.pr.new/create-nuxt@1072

npm i https://pkg.pr.new/nuxi@1072

npm i https://pkg.pr.new/@nuxt/cli@1072

commit: da1bb52

[codspeed-hq]

CodSpeed Performance Report

Merging #1072 will not alter performance

_{Comparing fix/windows-pipeline (da1bb52) with main (5b3d7a3)}

Summary

✅ 2 untouched