Skip to content

Commit 16e40dd

Browse files
author
Eric Lange
authored
Update README.md
1 parent 1e324e6 commit 16e40dd

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

LiquidCore/src/ios/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,16 +21,16 @@ and following the steps in the wizard.
2121

2222
```bash
2323
$ npm i liquidcore
24-
$ node node_modules/liquidcore/lib/cli.js init
24+
$ npx liquidcore init
2525
```
2626

2727
The `init` step will add some utility scripts and the `liquidcore` object to your `package.json` file. It will also create an example service called `example.js`, which will get packaged into your app. You can change / add files to be packaged by editing the `liquidcore.entry` property in your `package.json`.
2828

2929
#### Step 3: Configure your mobile app project
3030

3131
```bash
32-
$ npm run pod-config -- --target=<target> --podfile=<podfile>
33-
$ npm run bundler -- --platform=ios
32+
$ npx liquidcore pod-config -- --target=<target> --podfile=<podfile>
33+
$ npx liquidcore bundler -- --platform=ios
3434
$ pod install
3535
```
3636

@@ -53,7 +53,7 @@ where `<TARGET>` is the name of your `xcodeproj` (without the `.xcodeproj` exten
5353
Also, any time you add a new `liquidcore.entry` point in `package.json`, you must first run the bundler and then run `pod install` again. This is a quirk of how Cocoapods works with finding files. Those files must exist at installation time, or they will not be available in the pod, even if they are created later. So after adding a new `entry`, just do this part again:
5454

5555
```bash
56-
$ npm run bundler -- --platform=ios
56+
$ npx liquidcore bundler -- --platform=ios
5757
$ pod install
5858
```
5959

0 commit comments

Comments
 (0)