Nathan

@spion Same thing with the env var set. Here's some example code: Test: ``` js Test('MozQueue Integration', t => { // test setup return MozQueue.addUrls(urls) .then(jobs => Promise.all(map(n => waitForJobToFinish(n),...

Would you rather I try reproduce this in a test and submit a PR?

@spion I didn't get a chance to debug yet -- what is the solution?

The stack is empty for me, I just get the `at:` line: ``` stack: |- ```

@spion Ok, let me see what I can pull together for you

@spion Had inexplicable issues putting together a **simple** example. I'm not sure if this helps, but I did dig into `tape` and follow the trail. You're correct, in `Test.prototype.error` I...

@spion You're going to hate me. I was piping my output all this time into https://github.com/scottcorgan/tap-spec and I **think** this is causing the issue: (from `tap-out`) https://github.com/scottcorgan/tap-out/blob/master/lib/assert.js#L18

The raw output from `tap-out` is missing the stack trace which **is** present in the raw tap output: ``` "raw": " operator: error\n expected: |-\n undefined\n actual: |-\n [TypeError: Cannot...

@spion So many things to debug, too little time... It's on my radar!

@omsmith Is this related to browserify coughing things back up with: ``` Cannot read property 'match' of undefined while parsing file: ```