fix(node): don't use invalid port

[tidan-16]

🔗 Linked issue

nuxt/nuxt#22961

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ 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

I have change the condition a little to the node-server.ts file. It checks if the port is not null and if it is NaN, it puts the port (string) inside the path variable instead, wich resolve the issue for iisnode. Iisnode uses Named pipe instead of port numbers. Please check issue more infos

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[codecov]

Codecov Report

Merging #1697 (f8cb3c5) into main (5639f5b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1697   +/-   ##
=======================================
  Coverage   77.29%   77.29%           
=======================================
  Files          75       75           
  Lines        7893     7893           
  Branches      805      805           
=======================================
  Hits         6101     6101           
  Misses       1790     1790           
  Partials        2        2           

[tidan-16]

Any updates?

[pi0]

Hi dear @tidan-16. Thanks for spending time on making pull request and sorry for delay i needed time to properly setup a local IIS environment and probably check all possible cases.

#1783 fixes this issue specifically for iis-node that does this strange behavior.

I had been thinking of introducing this also as a general fix but seems unsafe for all node server presets to silently do such a conversation.