notifyReleaseStages prevents exception logging to console

If I use notifyReleaseStages to prevent sending reports when we’re running in dev, it also swallows the errors in the console. All I see is:

bugsnag.js:1581 Loaded!
bugsnag.js:281 Report not sent due to releaseStage/notifyReleaseStages configuration

For now we’re reporting all exceptions, even in dev as a workaround, and we’re overloading our quota. Could really use a fix for this one.

[snmaynard]

I wouldnt use notifyReleaseStages in that case. You can just return false in dev yourself from the callback

[broofa]

[Disclosure: I work with the OP, but have run into this problem independent of his report here]

The proposed workaround in the previous comment is not an adequate solution. Not only is it overly verbose, it drops essential information. E.g. In the sample below note how the first four lines of the original log output, that describe where the syntax error actually is, are not included in the workaround output.

At the risk of being overly dramatic, this sort of issue - where bug reporting software gets “in between” me and the code I’m trying to debug, quickly becomes a showstopper issue. Do with that what you will.

Original console output:

/Users/kieffer/tend/code/cellmate/sidekick/lib/BaseClient.js:293
    const realtimeItem = {time: now;
                                   ^

SyntaxError: Unexpected token ;
    at createScript (vm.js:80:10)
<< 14 stack frames clipped >>
    at Module.require (module.js:597:17)

“Workaround” output:

SyntaxError: Unexpected token ;
[ { file: 'vm.js',
    method: 'createScript',
    lineNumber: 80,
    columnNumber: 10,
    code: undefined,
    inProject: undefined },
<< 97 lines of stack info cut >> 
  { file: 'module.js',
    method: 'Module.require',
    lineNumber: 597,
    columnNumber: 17,
    code: undefined,
    inProject: undefined } ]