We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shell-script
In #648 @aomarks already mentions that the shell-script setting isn't supported yet, but there was no explicit issue for it yet.
I use shell-script=/bin/zsh for some projects because ** globs work as expected instead of the default shell (at least on macOS).
shell-script=/bin/zsh
**
For example when I run the following command with npm's default shell sh it only matches a subset of the expected match
sh
> node -e "console.log(process.argv)" src/**/*.test.ts [ '/path/to/my/project', 'src/test/a.test.ts', 'src/test/b.test.ts' ] >
but there's also a src/test/sub/a.test.ts which is not included in sh's expansion.
src/test/sub/a.test.ts
The actual command I noticed this with is tsx --test src/**/*.test.ts which uses tsx to run my tests written in TS with node's builtin test runner.
tsx --test src/**/*.test.ts
tsx
The text was updated successfully, but these errors were encountered:
Found a workaround: running the command through npx automatically picks up the npm settings.
npx
npx -c 'tsx --test src/**/*.test.ts'
Sorry, something went wrong.
workaround for wireit's missing script-shell support
7fb944a
google/wireit#832
No branches or pull requests
In #648 @aomarks already mentions that the
shell-script
setting isn't supported yet, but there was no explicit issue for it yet.I use
shell-script=/bin/zsh
for some projects because**
globs work as expected instead of the default shell (at least on macOS).For example when I run the following command with npm's default shell
sh
it only matches a subset of the expected matchbut there's also a
src/test/sub/a.test.ts
which is not included insh
's expansion.The actual command I noticed this with is
tsx --test src/**/*.test.ts
which usestsx
to run my tests written in TS with node's builtin test runner.The text was updated successfully, but these errors were encountered: