You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to have a script running on installation of a package and also on clone of the repo (setting up git hooks). So, I wrote a simple shell script:
#!/bin/bash
git config set core.hookspath $path
And use it in prepare and install script on package.json.
As I'm on windows, I've already defined my shell and script-shell o point to C:\\Program Files\\git\\bin\\bash.exe.
Therefore, is I run .hooks/setup, npm run prepare or npm install the script is correctly executed. But, if I do npm pack or npm publish, I get an error .hooks is not a valid command on the line C:\WINDOWS\system32\cmd.exe /d /s /c .hooks/setup.
Expected Behavior
The shell config should be honored, whatever the way it is used.
Steps To Reproduce
On windows
run npm config set script-shell "C:\\Program Files\\git\\bin\\bash.exe"
Have "prepare": "./test" on package.json's script
Have a simple test executable file with echo "ok" for example
This behaviour seems expected as prepare script run for git dependencies as well as directory for which it's doing pack. scriptshell flag seems to be left out of prepare script intentionally. Need to check some specifics around the issue and code here before it's marked Triaged again.
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
Hi,
I'm trying to have a script running on installation of a package and also on clone of the repo (setting up git hooks). So, I wrote a simple shell script:
And use it in
prepare
andinstall
script onpackage.json
.As I'm on windows, I've already defined my
shell
andscript-shell
o point toC:\\Program Files\\git\\bin\\bash.exe
.Therefore, is I run
.hooks/setup
,npm run prepare
ornpm install
the script is correctly executed. But, if I donpm pack
ornpm publish
, I get an error.hooks is not a valid command
on the lineC:\WINDOWS\system32\cmd.exe /d /s /c .hooks/setup
.Expected Behavior
The
shell
config should be honored, whatever the way it is used.Steps To Reproduce
npm config set script-shell "C:\\Program Files\\git\\bin\\bash.exe"
"prepare": "./test"
onpackage.json
'sscript
test
executable file withecho "ok"
for examplenpm run prepare
=> ✅ will print "ok"npm pack
=> ❌ will throw an errorEnvironment
The text was updated successfully, but these errors were encountered: