Closed boly38 closed 5 months ago
Hi @boly38, thanks for this issue, we'll try to reproduce it to understand what's wrong with the npm installation.
For now, considering your workspace, I can recommend adopting natives installation procedures:
@boly38 @lepapareil it should be fixed with Hurl npm package 4.3.2, @boly38 can you test it on Windows ?
Thanks for the report !
I just added a small remark to the PR, anyway 4.3.2 is working well, huge thanks 🙏 amazing support 👍
What is the current bug behavior?
Can't install hurl globally without having path issue (tested on git bash + WSL2)
Steps to reproduce
What is the expected correct behavior?
I expect having
hurl
in command current path (or at leasthurl.exe
)Execution context
hurl --version
):package version is version": "4.3.1" else
Possible fixes
What I noticed that could maybe help
exePath
=>execPath
(asexePath
producesReferenceError: exePath is not defined
)So with a fix on that variable, the error message become
NB: please replace
(REDACTED)
by current user home directory (ex.C:\Users\Jack\
)bin\
subfolderPossible workaround
here is the current workaround I'm using
But as alias is not available from some context (ex. Makefile), you could define a symlink instead (dont forget to remove it after the fix)