Bluebird warning
See original GitHub issue "connect-mongo": "^1.1.0",
"bluebird": "^3.3.1",
After every request I see in my log stacktrace including:
Warning: a promise was created in a handler but was not returned from it
at MongoStore.set (./node_modules/connect-mongo/src/index.js:240:18)
at Session.save (./node_modules/express-session/session/session.js:71:25)
at Session.save (./node_modules/express-session/index.js:331:15)
I think it’s better to fix it on connect-mongo level.
Thanks.
Issue Analytics
- State:
- Created 8 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Warning Explanations - Bluebird.js
Warning : a promise was rejected with a non-error. Due to a historic mistake in JavaScript, the throw statement is allowed to be...
Read more >Settings and Alerts - Bluebird
How do I set up or opt out of text or email alerts? · 1. Log in to your Bluebird account and go...
Read more >Eastern Bluebird Sounds - All About Birds
Songs. Eastern Bluebirds sing a fairly low-pitched, warbling song made up of several phrases, each consisting of 1-3 short notes. · Calls. The...
Read more >Bluebird Alert! Bluebirds Spotted at WBU - Wild Birds Unlimited
Bluebird Alert ! There were two bluebirds spotted at the Wild Birds Unlimited Franchise Support Center. These birds are a rare sight.
Read more >Bluebird warning "A promise was created in a handler but was ...
First, try and update all your dependencies. There's been a recent version of Bluebird, which fixed an issue involving this warning.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m still getting this.
I believe this is also because of express-session: https://github.com/expressjs/session/blob/master/index.js#L332
There’s nothing more to do with this module