Skip to content

Commit 3e1910c

Browse files
docs: fix npx usage to be scoped module
1 parent d421d4b commit 3e1910c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ JavaScript API usage can be found in the [API documentation](https://electron.gi
7272
Running Electron Packager from the command line has this basic form:
7373

7474
```
75-
npx electron-packager <sourcedir> <appname> --platform=<platform> --arch=<arch> [optional flags...]
75+
npx @electron/packager <sourcedir> <appname> --platform=<platform> --arch=<arch> [optional flags...]
7676
```
7777

7878
> **Note**:
@@ -97,7 +97,7 @@ detailed descriptions, see the [API documentation](https://electron.github.io/pa
9797
For flags that are structured as objects, you can pass each option as via dot notation as such:
9898

9999
```sh
100-
npx electron-packager --flag.foo="bar"
100+
npx @electron/packager --flag.foo="bar"
101101
# will pass in { flag: { foo: "bar"} } as an option to the Electron Packager API
102102
```
103103

@@ -138,10 +138,10 @@ foobar
138138
When one runs the following command for the first time in the `foobar` directory:
139139

140140
```
141-
npx electron-packager .
141+
npx @electron/packager .
142142
```
143143

144-
`electron-packager` will do the following:
144+
`@electron/packager` will do the following:
145145

146146
* Use the current directory for the `sourcedir`
147147
* Infer the `appname` from the `productName` in `package.json`

0 commit comments

Comments
 (0)