You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to be able to save my .nycrc as a .json file for automatic file type detection in VIM, Visual Studio Code, etc. This is a feature request, not a bug, but for consistency:
Expected Behavior
I put my configuration, JSON-formatted, in .nycrc.json and nyc respects that configuration when I run npm test, which in turn runs nyc nf mocha (nf for node-foreman)
Observed Behavior
nyc does not notice .nycrc.json as a configuration file (looking for .nycrconly), and falls back to default behavior.
Bonus Points! Code (or Repository) that Reproduces Issue
My repo (with .nycrc, no .json because as stated that doesn't work) can be found here.
Forensic Information
Operating System: MacBook Pro, macOS 10.12.4. zsh in Terminal for my command line, to be thorough. Environment Information: nvm running node 6.1.0; yarn for dependencies
The text was updated successfully, but these errors were encountered:
I'd like to be able to save my
.nycrc
as a.json
file for automatic file type detection in VIM, Visual Studio Code, etc. This is a feature request, not a bug, but for consistency:Expected Behavior
I put my configuration, JSON-formatted, in
.nycrc.json
andnyc
respects that configuration when I runnpm test
, which in turn runsnyc nf mocha
(nf
for node-foreman)Observed Behavior
nyc does not notice
.nycrc.json
as a configuration file (looking for.nycrc
only), and falls back to default behavior.Bonus Points! Code (or Repository) that Reproduces Issue
My repo (with
.nycrc
, no.json
because as stated that doesn't work) can be found here.Forensic Information
Operating System: MacBook Pro, macOS 10.12.4. zsh in Terminal for my command line, to be thorough.
Environment Information: nvm running node 6.1.0; yarn for dependencies
The text was updated successfully, but these errors were encountered: