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.
Allow `--nycrc-path` to be absolute
See original GitHub issueAt the moment --nycrc-path value must be relative. It would be great if this could be absolute as well.
My use case: I have a module with shared development tasks that I use in many libraries. One of those tasks is running tests with nyc. The nyc configuration is always the same, i.e. I want to specify it inside that shared module instead of inside each library.
I cannot use --cwd as it would impact test coverage (not just configuration loading). I.e. I need to use __dirname with an absolute path.
My current workaround is to use CLI flags instead of a configuration file, but a configuration file would be better.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 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
The new release of
find-uphas been made and will fix this issue once we’re able to release nyc@15. I’m going to close this issue as no further action will happen here, bumpingfind-upwill happen as part of a mass dependency update. Please follow #1104 for progress updates about the next release of nyc.@ehmicky this will be supported by the next release of
find-up, once that is released and we upgrade this issue will be fixed. The next version offind-upwill require node.js 8 so the plan is that this will be fixed in nyc@15. I can’t promise 15.0.0, it depends on when the nextfind-uprelease occurs.