Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issue when used with superagent-promise...

See original GitHub issue

When I use this with superagent-promise I get this error: Unhandled promise rejection TypeError: parserMethod is not a function(…)(anonymous function) @ es6.promise.js:112

I have no idea why! 😛

Issue Analytics

State:
Created 8 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

5reactions

eversoncommented, Dec 11, 2015

Ok, to give people more context. After 2h debugging, I finally solved on my end. It was happening because the regex was matching some other url, which had a different ‘http method’ and no callback.

I think what needs to improve here is to give a more clear error when this kind thing happens: “the url /foo/bar does not support ‘POST’”

sorry about making noise in the issue.

0reactions

DevSidecommented, May 24, 2017

Solved in 3.4.0 with #60

Top Results From Across the Web

Uncatched error when using Promises · Issue #1370 - GitHub

warn("Warning: superagent request was sent twice, because both .end() and .then() were called. Never call .end() if you use promises"); } this.

Promises with superagent - node.js - Stack Overflow

I am using node 6.3.0 and native promises (shouldn't matter). Also to be clear, my program is just hanging. – user3795202.

superagent-promise - npm

Start using superagent-promise in your project by running `npm i ... There are 202 other projects in the npm registry using superagent-promise.

superagent-promise - npm Package Health Analysis - Snyk

The npm package superagent-promise was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as...

superagent | Yarn - Package Manager

end(…) . Consider not using .end() at all, and migrating to promises by calling .then() instead. In Node, responses with unknown MIME type...