feat: read config from stdin

[dsanders11]

Went back and forth on whether to put the functionality in bin/lint-staged.js or lib/index.js. Decided on bin/lint-staged.js since it doesn't make full sense to include in the programmatic API since the library user can read the config from wherever they'd like and provide it as an object.

[codecov]

Codecov Report

Merging #918 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #918   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           18        18           
  Lines          608       609    +1     
  Branches       143       143           
=========================================
+ Hits           608       609    +1     

Impacted Files	Coverage Δ
lib/messages.js	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 78782f9...78f746b. Read the comment docs.

[iiroj]

What's your use-case for this feature? I'm fine with it, but the PR still needs some work. 👍

[dsanders11]

What's your use-case for this feature?

I'd like to be able to pipe in a config from the output of a previous command.

So, the simplest example: ./generate-lint-staged-config.py | lint-staged --config -

[dsanders11]

@iiroj, made your requested changes. Also scoped the new error message more tightly to just a read error on stdin and let JSON.parse silently fail until the config is validated in order to provide a more uniform experience.

[iiroj]

Thoughts, @okonet? Ready to merge, IMO.

[iiroj]

Thanks for the PR, @dsanders11!

[github-actions]

🎉 This PR is included in version 10.5.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀