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
At the moment, if spawn scripts are referencing locally installed npm executables, they are going to be not found.
spawn
spawn`tsx`
will produce "tsx program not found"
Users can workaround this by prefixing them with pnpm (or whatever package manager), e.g.
pnpm
spawn`pnpm tsx`
However, we should consider matching pnpm behaviour and just inject the appropriate path.
The text was updated successfully, but these errors were encountered:
feat: inject path to node_modules/.bin (fixes #35)
51b23b9
4fae2bf
dfbb0f5
🎉 This issue has been resolved in version 2.18.0 🎉
The release is available on:
Your semantic-release bot 📦🚀
Sorry, something went wrong.
No branches or pull requests
At the moment, if
spawn
scripts are referencing locally installed npm executables, they are going to be not found.will produce "tsx program not found"
Users can workaround this by prefixing them with
pnpm
(or whatever package manager), e.g.However, we should consider matching
pnpm
behaviour and just inject the appropriate path.The text was updated successfully, but these errors were encountered: