avbel / co-supertest Goto Github PK

With supertest now on 1.0.0, could you update your peer dependency to "^1.0.0"? Thanks.

Hi avbel,

Because one may use pure JSON APIs, it's more convenient to have the response body ready as JSON. Basically parse response.text as JSON and assign the result to response.body before passing the response to end().

I'm very happy to do a pull request if you like. Thanks

Since package.json has supertest: ~0.11.0, applications using a newer version of supertest (like ~0.12.1) will install a separate copy of supertest in node_modules. This means that co-supertest will monkey patch a different instance of the supertest module than what the parent app loads.

See:
https://www.npmjs.org/doc/files/npm-folders.html#cycles-conflicts-and-folder-parsimony
http://nodejs.org/api/modules.html#modules_module_caching_caveats

Hi,

Supertest has upgraded to 2.0.0.
Nothing breaks co-supertest, just need to update package.json