[windows] jco serve - operation not permitted, symlink

[pavelsavara]

PS C:\Dev\xxx-server> jco serve --jco-trace --jco-dir jco-temp c:/Dev/xxx-server/src/xxxServer/bin/Debug/net10.0/AppBundle/xxxServer.wasm

(jco serve) Error: EPERM: operation not permitted, symlink 'C:\Users\pavelsavara\AppData\Roaming\npm\node_modules\@bytecodealliance\jco\node_modules\@bytecodealliance\preview2-shim' -> 'C:\Dev\xxx-server\jco-temp\node_modules\@bytecodealliance\preview2-shim'
    at async symlink (node:internal/fs/promises:1005:10)
    at async runComponent (file:///C:/Users/pavelsavara/AppData/Roaming/npm/node_modules/@bytecodealliance/jco/src/cmd/run.js:99:7)
    at async file:///C:/Users/pavelsavara/AppData/Roaming/npm/node_modules/@bytecodealliance/jco/src/jco.js:224:9 {
  errno: -4048,
  code: 'EPERM',
  syscall: 'symlink',
  path: 'C:\\Users\\pavelsavara\\AppData\\Roaming\\npm\\node_modules\\@bytecodealliance\\jco\\node_modules\\@bytecodealliance\\preview2-shim',
  dest: 'C:\\Dev\\xxx-server\\jco-temp\\node_modules\\@bytecodealliance\\preview2-shim'
}

[vados-cosmonic]

Hey @pavelsavara thanks for the report, apologies for the delay here!

Is this an error that you were able to reproduce on any component, or is there something unique about the component.

A couple questions that would help me narrow this down:

• Did wasmtime serve work just fine for the component you're building?
• Do you get this same error in WSL?
• Do you have permissions to write to C:\Dev\xxx-server\jco-temp\node_modules\@bytecodealliance\preview2-shim ? I'd assume that you did but just want to ask to be absolutely sure (I wonder if a regular symlink command would work).

The only obvious symlink I see is actually covered by a try so I'm a bit surprised that you'd get that error especially on the line that is being reported (what version are you running on, that line must be quite different from what is now line 99) -- it makes sense that the EPERM made it through, but that seems to be working as intended.