Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add separate file to configure this plugin
See original GitHub issueHello @Hargne
First of all, thanks for this plugin. It’s been helpful to me 👍
I would like to suggest a feature request that allow the configuration to be set in a different file than package.json. It doesn’t have to be necessarily the Jest main config, as suggested in #12, but keeping it separate makes sense in the perspective of separation of concerns.
Unfortunately, package .json has become very bloated, where every JS plugin just “injects” its configuration into it, but this pattern only increases the size of the file while keeps it unmaintainable over time, particularly because you can’t just split it.
What do you think?
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Wow!! Awesome @Hargne !!
Thank you for working on that, I loved the new features!
Additional environment variables have been added in v0.6.0 (#22) that offers an alternative way to configure this plugin (following the design of jest-junit, as suggested by @pascalduez in this comment).
No option for an extra configuration file has been added. I believe that adding yet another config file with the sole purpose of configuring this plugin would both be redundant and confusing as plugins are normally configured within package.json.
Adding configuration to jest.config.js is not something that this plugin should do (please read this issue for an explanation).
Please re-open this issue if you don’t agree with this 😃