Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/adding-dependencies.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ This boilerplate uses a [two package.json structure](https://www.electron.build/
**Rule of thumb** is: all modules go into `./package.json` except for native modules, or modules with native dependencies or peer dependencies. Native modules, or packages with native dependencies should go into `./release/app/package.json`.

1. If the module is native to a platform (like node-postgres), it should be listed under `dependencies` in `./release/app/package.json`
2. If a module is `import`ed by another module, include it in `dependencies` in `./package.json`. See [this ESLint rule](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-extraneous-dependencies.md). Examples of such modules are `material-ui`, `redux-form`, and `moment`.
2. If a module is `imported` by another module, include it in `dependencies` in `./package.json`. See [this ESLint rule](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-extraneous-dependencies.md). Examples of such modules are `material-ui`, `redux-form`, and `moment`.
3. Otherwise, modules used for building, testing, and debugging should be included in `devDependencies` in `./package.json`.

### Further Readings
Expand Down