Closed garthk closed 9 years ago
I suspect that's caused by the errors
dependency. I'll have a look into it, and file a bug there if necessary.
The issue was indeed with the errors
dependency, I've submitted a pull request there that fixes it.
If this is a breaking issue for you, a workaround along the lines of the following (untested) should work, until it's fixed upstream:
if (typeof global.code !== "undefined") { var oldCode = global.code; }
var bhttp = require("node-bhttp");
if (typeof oldCode !== "undefined") { global.code = oldCode; }
An update for errors
has been pushed to npm, that should have solved this problem.