Christopher Hiller

For anyone who finds this issue: Mocha published a workaround for this in [v7.1.2](https://github.com/mochajs/mocha/releases/tag/v7.1.2). Depending on what versions of Mocha you intend to support, v6.0.0 of Mocha and newer should...

interested in this, might be able to help. cc @mikesherov

@ProLoser Honestly, this is great work. Bravo!

> I have, however, joined teams that have a god-awful number of directives This can happen for sure. Perhaps convention could be helpful here.

The necessary PR in `box-node-sdk` has been merged, and we're now awaiting a release.

this was released in v1.21.0 of box-node-sdk; I've updated the version requirement.

I spent a few mins exploring this, and while I think it's possible, it will take a good deal of fudging to deal with `_extends`. A problem is that there's...

You could also probably find a fanboy to rewrite it all in typescript. 😜

It appears [jasmine](https://npm.im/jasmine) needed an upgrade. Unfortunately, it's not backwards-compatible, so upgrading the tests from v1.x to v3.x syntax needs to happen. The [jasmine-node](https://npm.im/jasmine-node) module, which this project consumes, hasn't...

...also, the tests are written in such a way that a newer version is *especially* painful to use without pulling in [async](https://npm.im/async) or promisifying stuff. otherwise it'll devolve into "callback...