Skip to content

Commit ea1a62a

Browse files
feat(*): Rename package (due to conflict) (#4)
1 parent c2c0c42 commit ea1a62a

File tree

6 files changed

+16
-15
lines changed

6 files changed

+16
-15
lines changed

CHANGELOG.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
11
# Changelog
22

3-
Also see **[GitHub releases](https://github.com/dominique-mueller/exec-file/releases)**.
3+
Also see **[GitHub releases](https://github.com/dominique-mueller/exec-bin/releases)**.

README.md

+8-8
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
<div align="center">
22

3-
# exec-file
3+
# exec-bin
44

5-
**Run binary files in npm scripts.**
5+
**Run any binary files / executables within your npm scripts.**
66

77
</div>
88

@@ -13,34 +13,34 @@
1313
Running binary files / executables within npm scripts works if it's either part of an installed package (`node_modules/.bin`) or globally
1414
installed. A binary that exists someplace else, e.g. in the project root, cannot easily be executed.
1515

16-
**exec-file** is here to help! It's a (very!) small Node.js script that you can use to run binary files / executables, with all parameters
16+
**exec-bin** is here to help! It's a (very!) small Node.js script that you can use to run binary files / executables, with all parameters
1717
being forwarded automatically. Fantastic!
1818

1919
<br><br><br>
2020

2121
## How to install
2222

23-
You can get the **exec-file** via **npm** by adding it as a new _devDependency_ to your `package.json` file and running
23+
You can get the **exec-bin** via **npm** by adding it as a new _devDependency_ to your `package.json` file and running
2424
`npm install`. Alternatively, run the following command:
2525

2626
```bash
27-
npm install exec-file --save-dev
27+
npm install exec-bin --save-dev
2828
```
2929

3030
### Requirements
3131

32-
- **exec-file** requires **NodeJS 12** (or higher) to be installed
32+
- **exec-bin** requires **NodeJS 12** (or higher) to be installed
3333

3434
<br><br><br>
3535

3636
## How to use
3737

38-
Use **exec-file** within your `package.json` scripts. For example:
38+
Use **exec-bin** within your `package.json` scripts. For example:
3939

4040
```json
4141
{
4242
"scripts": {
43-
"build": "exec-file path/to/my/binary --first-parameter=foobar --second-boolean-parameter"
43+
"build": "exec-bin path/to/my/binary --first-parameter=foobar --second-boolean-parameter"
4444
}
4545
}
4646
```
File renamed without changes.

package-lock.json

+1-1
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

package.json

+5-4
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,24 @@
11
{
2-
"name": "exec-file",
3-
"description": "Run binary files in npm scripts.",
2+
"name": "exec-bin",
3+
"description": "Run any binary files / executables within your npm scripts.",
44
"version": "1.0.0",
55
"license": "MIT",
66
"repository": {
77
"type": "git",
8-
"url": "https://github.com/dominique-mueller/exec-file"
8+
"url": "https://github.com/dominique-mueller/exec-bin"
99
},
1010
"keywords": [
1111
"execute",
1212
"spawn",
1313
"run",
14+
"bin",
1415
"binary",
1516
"executable",
1617
"exe"
1718
],
1819
"type": "module",
1920
"bin": {
20-
"exec-file": "./bin/exec-file.js"
21+
"exec-bin": "./bin/exec-bin.js"
2122
},
2223
"scripts": {
2324
"build": "npm run build:clean && npm run build:ts && npm run build:assets",

tsconfig.json

+1-1
Original file line numberDiff line numberDiff line change
@@ -6,5 +6,5 @@
66
"removeComments": true,
77
"target": "es2017"
88
},
9-
"files": ["bin/exec-file.ts"]
9+
"files": ["bin/exec-bin.ts"]
1010
}

0 commit comments

Comments
 (0)