Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Add tip on how to execute the current package's binary #339

Merged
merged 3 commits into from Jul 1, 2019
Merged

Add tip on how to execute the current package's binary #339

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6bcf470
Add tip on how to execute the current package's binary
ehmicky Jul 1, 2019
35104af
Fix style
ehmicky Jul 1, 2019
d2aa790
Update readme.md
sindresorhus Jul 1, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
11 changes: 11 additions & 0 deletions readme.md
View file
Open in desktop
Expand Up @@ -499,6 +499,17 @@ const subprocess = execa('cat')
fs.createReadStream('stdin.txt').pipe(subprocess.stdin)
```

### Execute the current package's binary

```js
const {getBinPathSync} = require('get-bin-path');

const binPath = getBinPathSync();
const subprocess = execa(binPath);
```

This is useful when testing the current package's binary. As opposed to hard-coding the path to the binary, this validates that the `package.json` `bin` field is correctly set up.


## Related

Expand Down