Keith Cirkel

:tada:

Using the libraries.io api might be a good idea because it abstracts away all of the package management stuff that you'd otherwise have to do. I guess the only problem...

Firstly, I'm not sure of the intent of your code, but you should absolutely be rejecting with only `Error` instances, or subclass instances such as `TypeError`. rejecting Promises with strings...

@domenic Short answer: no. Longer answer: right now there is virtually no type checking inside chai. We are slowly doing this, and hopefully this will hopefully change to be enforced...

Yup. Just FYI we've split the majority of the check-error logic into it's own module - https://github.com/chaijs/check-error - which is on npm and can be used like any normal dependency....

Yeah... it's mostly argument munging or negotiating with the check-error API which we didn't want to black box. Sadly providing 10 different ways for people to assert on errors can...

You can have alteast half of the questions answered for you by having a file called .gitconfig in your home directory, and including this: ``` [gitflow "prefix"] feature = feature/...

LGTM, but I might leave it to @jashkenas to merge

Looks like a good change to me, but I'd like @jashkenas to take a look and do the merge

At the risk of sounding like Wikipedia, is this language even notable enough to be featured? I know it's only a small change but I'd rather avoid a bloated languages.json...