fix(dev): use fs.statsSync to determine existence of socket path

[chengzhuo5]

🔗 Linked issue

#1115
nuxt/nuxt#15164

❓ 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

In #1115, use accessSync to ensure socketPath exists. However, in some special file systems (such as the sandbox provided by security software), accessSync cannot determine whether the socketPath exists and will block dev server, but statsSync can determine correctly.

📝 Checklist

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

[pi0]

Thanks for PR.

(such as the sandbox provided by security software

Can you please elaborate more which security software? I need to reproduce.

[chengzhuo5]

Thanks for PR.

(such as the sandbox provided by security software

Can you please elaborate more which security software? I need to reproduce.

This is a sandbox software named DataCloak, which can only be used by the enterprise that purchased it, so you cannot reproduce this issue.

DataCloak on Windows will use the Windows Filtering Platform driver to take over any IO operations. When fs.accessSync("\\?\pipe\" or "\\.\pipe\") is called, DataCloak looks for it from the file system, but apparently it doesn't exist.

[pi0]

Thanks for the explanation dear @chengzhuo5. It seems a bug/issue with this protection software and if widely unsolvable, we might propose fixes to lower-level layers (Node.js).

I would suggest that you contact them (i also submitted a request pointing to this PR) about it maybe they have some explanation or consider fixing it. A simpler Node.js script to reproduce might give them better context.

I have made two relevant trackers also, let's see what comes first:

• Feature flag to make dev worker use random port instead of sockets #2365 (adding support for port listening)
• Add utilities to make/check unix socket get-port-please#91 (it would still use one access but if we can reproduce sandbox issue, we can put the solution in there)