Support configuration from 'nodemonConfig' in package.json #1028
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Implements loading configuration options from the `nodemonConfig` value in the package.json, nodemon.json is still preferred before looking at the new option. Also includes tests. Closes remy#873
Add to both the README and `nodemon --help config`.
|
I personally never put the config for nodemon or any of the packages mentioned above in package.json. I always choose to set config on a separate file. |
|
+1 always prefer config in one place and as package.json is a load of config it makes sense. Helps keep config relatively small as well. |
|
I try and centralize all my configs (Babel, ESLint, StandardJS, Browserlist, etc.) in a single package.json file for my apps, so this would be neat. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow
nodemonConfigto be used in a projectspackage.json.This matches the option of a lot of other development tools - ESLint as
eslintConfig, JSHint asjshintConfig, JSCS asjscsConfigbut to name a few...!This feature is entirely additive - if the
--config <file>is specified or there's a localnodemon.jsonthennodemonConfigin thepackage.jsonwill be ignored.