Skip to content

Commit

Permalink
docs: update install-app-deps command usage example (#1729)
Browse files Browse the repository at this point in the history
update install-app-deps usage example on Two package.json Structure docs to comply with module's warning message
  • Loading branch information
araujoigor authored and develar committed Jun 22, 2017
1 parent c99c3a0 commit 0a98870
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/tutorials/Two package.json Structure.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,4 +15,4 @@ Why?

Please see [Loading App Dependencies Manually](https://github.com/electron-userland/electron-builder/wiki/Loading-App-Dependencies-Manually) and [#379](https://github.com/electron-userland/electron-builder/issues/379#issuecomment-218503881).

If you use the two-package.json project structure, you'll only have your `devDependencies` in your development `package.json` and your `dependencies` in your app `package.json`. To ensure your dependencies are always updated based on both files, simply add `"postinstall": "install-app-deps"` to your development `package.json`. This will basically automatically trigger an `npm install` within your app directory so you don't have to do this work every time you install/update your dependencies.
If you use the two-package.json project structure, you'll only have your `devDependencies` in your development `package.json` and your `dependencies` in your app `package.json`. To ensure your dependencies are always updated based on both files, simply add `"postinstall": "electron-builder install-app-deps"` to your development `package.json`. This will basically automatically trigger an `npm install` within your app directory so you don't have to do this work every time you install/update your dependencies.

0 comments on commit 0a98870

Please sign in to comment.