Benjamin E. Coe

icon indicating a website link https://twitter.com/benjamincoe icon indicating an email [email protected]

icon location Waterloo icon location Co-founded Attachments.me, early employee at npm Inc. Maintains yargs, Istanbul, contributes to Node.js. Currently product at Sentry.

Results 350 comments of Benjamin E. Coe

Merging multiple converted coverage reports together for the same file results in a mismatch between the number of properties in `branchMap` and `b`.

@JustinChristensen one problem is that v8 output won't necessarily have all the same branch information, as it collapses together consecutive blocks. I think this problem might be better solved by...

Support webpack:// in the `sourceRoot` option

@tomardern what's the expected behavior? should we just be dropping `webpack://` in this case?

Error while trying to read the map file

@rwalle I would consider a patch for this. I think we should warn on the console as well as setting `this.rawSourceMap = null`, if we have metadata indicating a source...

Add the variable to make a tree for b-form-select

@ab2d3e8 I'm not following what you're trying to do, are you sure this is the right library?

Call options are not documented and non-obvious

Hey @jayp 👋 we're in the process of [converting this library to TypeScript](https://github.com/googleapis/nodejs-tasks/pull/317), which should help a ton with regards to documenting these available options.

Fix failing build and update npm packages.

@bhargav175 would love the help getting builds running more smoothly 👍 and appreciate any other contributions you would like to make to this site. We worked with the creator of...

document how and when subprocesses send coverage to nyc & that coverage will be lost for SIGKILLed processes

@jedwards1211 seems like a great idea to document this better, I'll update this thread with some thorough information about how coverage is collected when I have a few more cycles...

4.1.2 Breaks dependents, as hosted-git-info 4.0.0 has a breaking change.

@dangreen @designbyadrian thank you for the bug report, are you able to pin the dependency for the time being? Hopefully @hutson or myself can dig into soon :clap:

Create <whitespace> and <newline>, (, ), etc nodes rather than throwing out tokens

> Am I missing something here? The implementation looks right, but I think it is just miss-represented in the grammar spec. @wesleytodd this was intentional on my part, I see...

Create <whitespace> and <newline>, (, ), etc nodes rather than throwing out tokens

@byCedric @wesleytodd having been playing around a bit with a tree visitor, it jumps out at me that we'll probably also want to add `(`, `)`, and any other tokens...