"No workspaces found" when generating signing key.

[privatedev11]

When I run tauri signer generate -w ~/.tauri/myapp.key to generate a key, I get the following:

npm ERR! No workspaces found:
npm ERR!   --workspace=~/.tauri/myapp.key

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\USER\AppData\Local\npm-cache\_logs\2023-01-07T13_16_19_707Z-debug-0.log

username has been removed for privacy reasons

How can I fix this? Am I doing something wrong?
I am quite new to Tauri and Node.js so apologies if it is a noob error.

[FabianLars]

npm needs -- to forward the args to tauri, like npm run tauri signer generate -- -w ~/.tauri/myapp.key
Also note that ~/ doesn't work on Windows, it will instead create a literal ~ folder in your current directory

p.s. i'm in the process of rewriting the guide, including these parts to hopefully make it easier & more failproof.

[privatedev11]

Thank you, that has worked.

[Emmanuel97423]

Hi! i've same issue on windows:

npm run tauri signer generate -- -w $HOME/.tauri/myapp.key

npm run tauri signer generate -- -w $HOME/.tauri/myapp.key
npm ERR! No workspaces found:
npm ERR!   --workspace=C:\Users\Epokw/.tauri/myapp.key

Someone can help me ? :)

[Emmanuel97423]

Yes ! Thank you its ok !
Can you explain me this issue ?

[FabianLars]

I have no idea tbh. Normally the extra -- is all you need. Maybe your specific npm version has an issue?

[Roalkege]

Hey I have the exact issue.
The npm run command does not work but the npx command works for me.

[domsleee]

It seems that two -- are required in some installations of powershell, this command works for me:

npm run tauri signer generate -- -- -w $HOME/.tauri/myapp.key

Explained in this comment: npm/cli#6041 (comment)

If npm points to a ps1 script, calling the ps1 script strips away one of the --, before it calls the npm binary.

It can be checked with this command, if the output ends with .ps1, two -- are required:

❯ which npm
C:\Users\user\scoop\apps\nvs\current\nodejs\default\npm.ps1

[domsleee]

More info about powershell npm.ps1 issues in npm/cli#3136