Corey Farrell

@akoidan I've just released a new beta of nyc which contains at least one fix to source-map processing. Could you give this a try? I've seen `TypeError: Cannot read property...

@akoidan I'm very busy so I have to ask for your patience.

Have you tried using `encodeURI` on the password? ```js let n = Nano('http://admin:' + encodeURI('g[?6asdwrF') + '@localhost:5984'); ``` I suspect the problem is that the URL you used is not...

Thank you for the 'greater than any version matching 3.x' explanation, that makes sense to me. Ultimately `>3` is the same as `>3.x` or `>3.x.x`, not the same as `>3.0`...

> This LGTM, assuming that it still has full coverage after making the requested modification to the tests. On it's own nyc will not produce coverage for ES modules loaded...

One more comment on ESM coverage, the experimental module I mentioned does not work with nyc 14 (used by the current version of tap). It's @isaacs call but I think...

I'm not able to reproduce this by creating `mytest.js` with the following content: ```js const actions = { /* istanbul ignore next */ myMethod () { return true } };...

You are using `babel-jest@^23.6.0` which uses `[email protected]`. That was the last version to use babel 6, would it be possible for you to update to `babel-jest@^24` and replace `babel-core` with...

Sorry I haven't had a chance to dig deeper, my time has been extremely limited. One thing I just tested: ```js const obj = { /* istanbul ignore next */...

The `nyc report` doesn't (can't) perform instrumentation, it only reports. Try the following `nyc --require ./babel-register.js --instrument=false --source-map=false --all=true true`. What this does is cause `nyc` to run, generate coverage...