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
The postinstall script in the single template's package.json fails on install
To Reproduce
npx @stricli/create-app@latest --template single my-app
cd my-app
npm install
Expected behavior
Install completes with no errors
Actual behavior is (npm install proceeds as normal, then):
> my-app@0.0.0 postinstall
> npx @stricli/auto-complete@latest install my-app __my-app_bash_complete
Too many arguments, expected 1 but encountered "__my-app_bash_complete"
and exit code 252
Environment:
MacOS X, bash
node v18.19.0, npm 10.2.3
Additional context
I think the command should have been: npx @stricli/auto-complete@latest install --bash my-app __my-app_bash_complete (i.e. it's missing the --bash bit)
I've seen the same failure when trying to use pnpm dlx.
Also, the multiple command template fails in a different way when using pnpm, because the in-project package.json "bin" entries are't accessible from the path of the "scripts" by default). But that's a separate issue relating to pnpm support - possibly related to pnpm/pnpm#7461 - where the workaround is to add an entry matching the bin entry to the scripts. I just mention it here because that's what I'm actually using, even though the above reproduction happens on npm
The text was updated successfully, but these errors were encountered:
Describe the bug
The postinstall script in the
single
template's package.json fails on installTo Reproduce
Expected behavior
Install completes with no errors
Actual behavior is (npm install proceeds as normal, then):
and exit code 252
Environment:
MacOS X, bash
node v18.19.0, npm 10.2.3
Additional context
I think the command should have been:
npx @stricli/auto-complete@latest install --bash my-app __my-app_bash_complete
(i.e. it's missing the--bash
bit)I've seen the same failure when trying to use
pnpm dlx
.Also, the multiple command template fails in a different way when using pnpm, because the in-project package.json "bin" entries are't accessible from the path of the "scripts" by default). But that's a separate issue relating to pnpm support - possibly related to pnpm/pnpm#7461 - where the workaround is to add an entry matching the
bin
entry to thescripts
. I just mention it here because that's what I'm actually using, even though the above reproduction happens on npmThe text was updated successfully, but these errors were encountered: