The return value of the promise constructor is ignored.
The resolve
function also returns undefined.
This was first specified in the promise constructor spec and later in the ES2015 (ES6) language specification.
More Related Contents:
- Correct Try…Catch Syntax Using Async/Await
- What’s wrong with awaiting a promise chain?
- Difference between defer().promise and Promise
- JavaScript Promises – reject vs. throw
- How to include multiple js files using jQuery $.getScript() method
- Asynchronous operations in constructor
- Node JS Promise.all and forEach
- Wait for multiple promises to finish
- how to break promise chain
- How to check if an object is a Promise?
- Why are exceptions used for rejecting promises in JS? [closed]
- JavaScript array .reduce with async/await
- What do double brackets mean in javascript and how to access them
- Chaining Observables in RxJS
- Node exits without error and doesn’t await promise (Event callback)
- Nodejs express and promises not doing what I expect
- How do I use Bluebird with Angular?
- What is the relationship between event loop and Promise [duplicate]
- Why is `.catch(err => console.error(err))` discouraged?
- How to do promise.all for array of array of promises?
- Do Javascript promises block the stack
- What happens if i reject / resolve multiple times in Kriskowal’s q?
- Javascript – if with asynchronous case
- Using mongoose promises with async/await
- Is there a way to tell if an ES6 promise is fulfilled/rejected/resolved? [duplicate]
- How to use Promise.all with an object as input
- Promise and Promise.all(array) executed before array fulfilled [duplicate]
- Are JavaScript forever-pending promises bad?
- Why does javascript ES6 Promises continue execution after a resolve?
- How to Promisify this function – nodejs [duplicate]