Allow config to be read from rc file

[greg-a-smith]

It would be nice to be able to offload the "config" section in package.json into its own rc dot-file similar to how eslint uses .eslintrc.

[KeithPepin]

Excellent, I've been considering this recently so thanks for spurring it forward. To preserve backwards compatibility, do you think I should fall back to the config section of the package.json if the .rc file wasn't present? Or should this just be a breaking change to the next version?

Either way, I'm making this happen, just trying to consider the extra documentation, etc.

The other reason for doing this is to make the configuration process the same for husky and ghooks, then it is simply a matter of configuring your trigger in either based on how those modules work.

[greg-a-smith]

Always the million dollar question, right? 😄 I could go either way on this. It does seem like a good candidate for a breaking change especially since this specific change wouldn't be exposing any new "features". That way, you don't need to hang on to old code and old documentation. But, if you think it's better to leave backward compatibility, I wouldn't argue.

[KeithPepin]

Greg, just FYI, I've got the new version coded up. I'm just taking some time to update the documentation and then I'll close both these open issues and release it. Another day or so to get that done amidst family life and you'll have it in hand. I ended up just extending the existing code to give users the option of a .json file for configuration or keeping the config in the package.json, so that in itself won't be a breaking change, but I also updated things to ES6 which may be a breaking change for some folks given the higher requirements for node (now require >=4.8.x). I'll remove the config in package.json over time.

[greg-a-smith]

Sounds good. We have it working with the config in package.json so whenever the new version is released, we'll give it a shot with the separate config file.

[bcullman]

did this feature ever release?