Closed daliboris closed 1 year ago
execa is a new dependency introduced with the edit feature. There might be an issue with this. You could try and install the version before that.
npm install -g @existdb/xst@1.5.0
Also, I do not really understand what you mean by adding it to npm.
You're right, version 1.5.0 works fine.
I wasn't adding it to npm. I just needed to add the path to the npm
repository to the PATH variable (this information was missing in my report, sorry) on my Windows machine, otherwise running the xst
command didn't work.
@daliboris hmm, it seems that xst --version
now fails for me too with xst 1.6.0.
Thanks for reporting this. The execa dependency was missing in package.json (!)
:tada: This issue has been resolved in version 1.6.1 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
What happened?
After installing
xst
globally, setting the path to thenpm
repository (C:\Users\<User>\AppData\Roaming\npm
) and runningxst
from Windows Powershell Command, or a Command Prompt the errorCannot find package 'execa'
is thrown.Xst program will not run.
System Information
Relevant shell output