Using wireit with a drive mapped by sshfs-win results in an operation not permitted error

I have a resource on my local network that is mapped to a drive using sshfs-win (https://github.com/winfsp/sshfs-win). When trying to use wireit, I experience the following error:

> wireit

node:internal/process/esm_loader:97
    internalBinding('errors').triggerUncaughtException(
                              ^

[Error: EPERM: operation not permitted, mkdir 'D:\.wireit\736f72742d7061636b6167652d6a736f6e'] {
  errno: -4048,
  code: 'EPERM',
  syscall: 'mkdir',
  path: 'D:\\.wireit\\736f72742d7061636b6167652d6a736f6e'
}

Mapping the same resource using Samba allows wireit to run correctly.

I'm not sure if it's an issue with sshfs-win, or if there is something that can be done with wireit. The error is pretty opaque, and I'm not sure if it's because of a file lock, or length of the directory name or something else.

https://github.com/google/wireit/issues/624

Reproduce the failure with the sshfs-win mapped drive and compare it with the working Samba mapping, starting from the reported mkdir operation and EPERM path. Determine whether the limitation is in sshfs-win or wireit, then document or implement a fix and verify wireit runs on the mapped drive.