usdk icon indicating copy to clipboard operation
usdk copied to clipboard

[Bug]: File path issues related to libopus.wasm on Windows

Open Deletus1 opened this issue 10 months ago • 3 comments

Product

USDK (Upstreet Agents SDK)

What happened?

Windows Bug!

USDK on the CLI is mapping drive letters incorrectly to the path of "libopus.wasm".

for e.g.: path: 'D:\C:\Users\<Your_Username_Goes_Here>\AppData\Roaming\npm\node_modules\usdk\packages\upstreet-agent\packages\codecs\packages\libopusjs\libopus.wasm'

Due to this, USDK CLI commands cannot be used/run.

Version

0.0.110

What is your environment?

Node Version: 23.2.0, NPM Version: 10.9.0, OS: Windows, Terminal: cmd

Link to original discussion

No response

Relevant log output

Error: ENOENT: no such file or directory open 'D:\C:\Users<Your_Username_Goes_Here>\AppData\Roaming\npm\node_modules\usdk\packages\upstreet-agent\packages\codecs\packages\libopusjs\libopus.wasm'

Deletus1 avatar Mar 03 '25 19:03 Deletus1

Looks like a fairly simple issue, seems like we're assuming the C drive.

SaadBazaz avatar Mar 03 '25 19:03 SaadBazaz

It seems like an issue in import.meta.dirname. @AbdurrehmanSubhani @mavisakalyan - What do you think?

SaadBazaz avatar Mar 03 '25 19:03 SaadBazaz

Looks like a fairly simple issue, seems like we're assuming the C drive.

Considering my current working directory is in my D drive, but as I installed usdk globally, it should be looking in my C drive. It seems to be taking the current working directory's drive letter and appending it to the location of usdk. (The location of usdk is correct, but in this scenario, the drive letter doesn't need to be appended i guess.)

Deletus1 avatar Mar 03 '25 21:03 Deletus1