Why does the resolve message appear first? Unicorn Meta Zoo #1: Why another podcast? Announcing the arrival of Valued Associate #679: Cesar Manara Data science time! April 2019 and salary with experience The Ask Question Wizard is Live!Why is using “for…in” with array iteration a bad idea?How does JavaScript .prototype work?How do I make the first letter of a string uppercase in JavaScript?What does “use strict” do in JavaScript, and what is the reasoning behind it?What is JSONP, and why was it created?Why does Google prepend while(1); to their JSON responses?Why does ++[[]][+[]]+[+[]] return the string “10”?How does data binding work in AngularJS?How does Facebook disable the browser's integrated Developer Tools?ECMAScript 6 Chaining Promises

What do you call the part of a novel that is not dialog?

Split coins into combinations of different denominations

Are all CP/M-80 implementations binary compatible?

What's the difference between using dependency injection with a container and using a service locator?

Is it OK if I do not take the receipt in Germany?

How do I check if a string is entirely made of the same substring?

std::is_constructible on incomplete types

What's parked in Mil Moscow helicopter plant?

c++ diamond problem - How to call base method only once

A Paper Record is What I Hamper

Additive group of local rings

What is the ongoing value of the Kanban board to the developers as opposed to management

How to not starve gigantic beasts

How to avoid introduction cliches

Is it acceptable to use working hours to read general interest books?

I preordered a game on my Xbox while on the home screen of my friend's account. Which of us owns the game?

What is /etc/mtab in Linux?

Check if a string is entirely made of the same substring

Are there moral objections to a life motivated purely by money? How to sway a person from this lifestyle?

finding a tangent line to a parabola

Are these square matrices always diagonalisable?

What is a 'Key' in computer science?

"Rubric" as meaning "signature" or "personal mark" -- is this accepted usage?

Is a 5 watt UHF/VHF handheld considered QRP?



Why does the resolve message appear first?



Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar Manara
Data science time! April 2019 and salary with experience
The Ask Question Wizard is Live!Why is using “for…in” with array iteration a bad idea?How does JavaScript .prototype work?How do I make the first letter of a string uppercase in JavaScript?What does “use strict” do in JavaScript, and what is the reasoning behind it?What is JSONP, and why was it created?Why does Google prepend while(1); to their JSON responses?Why does ++[[]][+[]]+[+[]] return the string “10”?How does data binding work in AngularJS?How does Facebook disable the browser's integrated Developer Tools?ECMAScript 6 Chaining Promises



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








11















I'm trying to wrap my mind around promises in JavaScript. I was under the illusion that once a Promise was resolved it could never go back to rejected. To test that I wrote a little script. I see that the first messages that come back are the resolve messages "1 resolve 2" etc. I expected the first message to be "0 reject 1".



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>

let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)

)

p.then((message) =>
console.log(message)
).catch((message) =>
console.log(message)
)



at the console:



[Log] 1 resolve 2
[Log] 3 resolve 2
[Log] 5 resolve 2
[Log] 7 resolve 2
[Log] 9 resolve 2
[Log] 0 reject 1
[Log] 2 reject 1
[Log] 4 reject 1
[Log] 6 reject 1
[Log] 8 reject 1
< Promise status: "pending"


thanks for you help....



After reading



https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/then



I got to this code. The catch is removed.



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>

let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)


)

p.then((message) =>
console.log(message)
, failed =>
console.log(failed)
)



at the console:



[Log] 0 reject 1
[Log] 1 resolve 2
[Log] 2 reject 1
[Log] 3 resolve 2
[Log] 4 reject 1
[Log] 5 resolve 2
[Log] 6 reject 1
[Log] 7 resolve 2
[Log] 8 reject 1
[Log] 9 resolve 2
< Promise status: "pending"









share|improve this question



















  • 3





    You are creating new promise on every iteration

    – brk
    Apr 17 at 18:44






  • 5





    Is your question why you see the resolved promises before the rejected? I.e. why is the output [1, 3, 5, 7, 9, 0, 2, 4, 6, 8] instead of [0, 1, 2, 3, 4, ...]?

    – junvar
    Apr 17 at 18:54






  • 2





    Yes Junvar. That is my question.

    – Edwin
    Apr 17 at 18:58






  • 5





    99% sure it's because the .then and .catch each take a tick on the event loop. So the rejections are all a single tick behind your resolves.

    – jhpratt
    Apr 17 at 19:07






  • 1





    I'd add that 1% to that.

    – Michał Kapracki
    Apr 17 at 19:38

















11















I'm trying to wrap my mind around promises in JavaScript. I was under the illusion that once a Promise was resolved it could never go back to rejected. To test that I wrote a little script. I see that the first messages that come back are the resolve messages "1 resolve 2" etc. I expected the first message to be "0 reject 1".



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>

let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)

)

p.then((message) =>
console.log(message)
).catch((message) =>
console.log(message)
)



at the console:



[Log] 1 resolve 2
[Log] 3 resolve 2
[Log] 5 resolve 2
[Log] 7 resolve 2
[Log] 9 resolve 2
[Log] 0 reject 1
[Log] 2 reject 1
[Log] 4 reject 1
[Log] 6 reject 1
[Log] 8 reject 1
< Promise status: "pending"


thanks for you help....



After reading



https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/then



I got to this code. The catch is removed.



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>

let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)


)

p.then((message) =>
console.log(message)
, failed =>
console.log(failed)
)



at the console:



[Log] 0 reject 1
[Log] 1 resolve 2
[Log] 2 reject 1
[Log] 3 resolve 2
[Log] 4 reject 1
[Log] 5 resolve 2
[Log] 6 reject 1
[Log] 7 resolve 2
[Log] 8 reject 1
[Log] 9 resolve 2
< Promise status: "pending"









share|improve this question



















  • 3





    You are creating new promise on every iteration

    – brk
    Apr 17 at 18:44






  • 5





    Is your question why you see the resolved promises before the rejected? I.e. why is the output [1, 3, 5, 7, 9, 0, 2, 4, 6, 8] instead of [0, 1, 2, 3, 4, ...]?

    – junvar
    Apr 17 at 18:54






  • 2





    Yes Junvar. That is my question.

    – Edwin
    Apr 17 at 18:58






  • 5





    99% sure it's because the .then and .catch each take a tick on the event loop. So the rejections are all a single tick behind your resolves.

    – jhpratt
    Apr 17 at 19:07






  • 1





    I'd add that 1% to that.

    – Michał Kapracki
    Apr 17 at 19:38













11












11








11


3






I'm trying to wrap my mind around promises in JavaScript. I was under the illusion that once a Promise was resolved it could never go back to rejected. To test that I wrote a little script. I see that the first messages that come back are the resolve messages "1 resolve 2" etc. I expected the first message to be "0 reject 1".



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>

let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)

)

p.then((message) =>
console.log(message)
).catch((message) =>
console.log(message)
)



at the console:



[Log] 1 resolve 2
[Log] 3 resolve 2
[Log] 5 resolve 2
[Log] 7 resolve 2
[Log] 9 resolve 2
[Log] 0 reject 1
[Log] 2 reject 1
[Log] 4 reject 1
[Log] 6 reject 1
[Log] 8 reject 1
< Promise status: "pending"


thanks for you help....



After reading



https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/then



I got to this code. The catch is removed.



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>

let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)


)

p.then((message) =>
console.log(message)
, failed =>
console.log(failed)
)



at the console:



[Log] 0 reject 1
[Log] 1 resolve 2
[Log] 2 reject 1
[Log] 3 resolve 2
[Log] 4 reject 1
[Log] 5 resolve 2
[Log] 6 reject 1
[Log] 7 resolve 2
[Log] 8 reject 1
[Log] 9 resolve 2
< Promise status: "pending"









share|improve this question
















I'm trying to wrap my mind around promises in JavaScript. I was under the illusion that once a Promise was resolved it could never go back to rejected. To test that I wrote a little script. I see that the first messages that come back are the resolve messages "1 resolve 2" etc. I expected the first message to be "0 reject 1".



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>

let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)

)

p.then((message) =>
console.log(message)
).catch((message) =>
console.log(message)
)



at the console:



[Log] 1 resolve 2
[Log] 3 resolve 2
[Log] 5 resolve 2
[Log] 7 resolve 2
[Log] 9 resolve 2
[Log] 0 reject 1
[Log] 2 reject 1
[Log] 4 reject 1
[Log] 6 reject 1
[Log] 8 reject 1
< Promise status: "pending"


thanks for you help....



After reading



https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/then



I got to this code. The catch is removed.



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>

let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)


)

p.then((message) =>
console.log(message)
, failed =>
console.log(failed)
)



at the console:



[Log] 0 reject 1
[Log] 1 resolve 2
[Log] 2 reject 1
[Log] 3 resolve 2
[Log] 4 reject 1
[Log] 5 resolve 2
[Log] 6 reject 1
[Log] 7 resolve 2
[Log] 8 reject 1
[Log] 9 resolve 2
< Promise status: "pending"






javascript es6-promise






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 18 at 1:27









Boann

37.6k1291123




37.6k1291123










asked Apr 17 at 18:39









EdwinEdwin

685




685







  • 3





    You are creating new promise on every iteration

    – brk
    Apr 17 at 18:44






  • 5





    Is your question why you see the resolved promises before the rejected? I.e. why is the output [1, 3, 5, 7, 9, 0, 2, 4, 6, 8] instead of [0, 1, 2, 3, 4, ...]?

    – junvar
    Apr 17 at 18:54






  • 2





    Yes Junvar. That is my question.

    – Edwin
    Apr 17 at 18:58






  • 5





    99% sure it's because the .then and .catch each take a tick on the event loop. So the rejections are all a single tick behind your resolves.

    – jhpratt
    Apr 17 at 19:07






  • 1





    I'd add that 1% to that.

    – Michał Kapracki
    Apr 17 at 19:38












  • 3





    You are creating new promise on every iteration

    – brk
    Apr 17 at 18:44






  • 5





    Is your question why you see the resolved promises before the rejected? I.e. why is the output [1, 3, 5, 7, 9, 0, 2, 4, 6, 8] instead of [0, 1, 2, 3, 4, ...]?

    – junvar
    Apr 17 at 18:54






  • 2





    Yes Junvar. That is my question.

    – Edwin
    Apr 17 at 18:58






  • 5





    99% sure it's because the .then and .catch each take a tick on the event loop. So the rejections are all a single tick behind your resolves.

    – jhpratt
    Apr 17 at 19:07






  • 1





    I'd add that 1% to that.

    – Michał Kapracki
    Apr 17 at 19:38







3




3





You are creating new promise on every iteration

– brk
Apr 17 at 18:44





You are creating new promise on every iteration

– brk
Apr 17 at 18:44




5




5





Is your question why you see the resolved promises before the rejected? I.e. why is the output [1, 3, 5, 7, 9, 0, 2, 4, 6, 8] instead of [0, 1, 2, 3, 4, ...]?

– junvar
Apr 17 at 18:54





Is your question why you see the resolved promises before the rejected? I.e. why is the output [1, 3, 5, 7, 9, 0, 2, 4, 6, 8] instead of [0, 1, 2, 3, 4, ...]?

– junvar
Apr 17 at 18:54




2




2





Yes Junvar. That is my question.

– Edwin
Apr 17 at 18:58





Yes Junvar. That is my question.

– Edwin
Apr 17 at 18:58




5




5





99% sure it's because the .then and .catch each take a tick on the event loop. So the rejections are all a single tick behind your resolves.

– jhpratt
Apr 17 at 19:07





99% sure it's because the .then and .catch each take a tick on the event loop. So the rejections are all a single tick behind your resolves.

– jhpratt
Apr 17 at 19:07




1




1





I'd add that 1% to that.

– Michał Kapracki
Apr 17 at 19:38





I'd add that 1% to that.

– Michał Kapracki
Apr 17 at 19:38












4 Answers
4






active

oldest

votes


















4














You can see what's going on under the hood by using your the console of your browser's dev tools and, possibly, setting break points (this articles might be helpful if u're using Chrome or Firefox):



enter image description here



As you can see, all your 10 promises are created before any of them are executed (resolve/reject).



Interestingly, in your code the resolved promises are handled first.



If you define the handlers in two separate definitions, you'll get the expected results:



p.then((message) => 
console.log(message)
)
p.catch((message) =>
console.log(message)
)


Output:



enter image description here






share|improve this answer























  • i am so surprize by the conclusion of your answer. I never imagined than chain vs multiple instruction can have this huge impact. Really good sharing

    – Yanis-git
    Apr 17 at 19:55


















2














The point is, Promises are made to be used as Asynchronous calls, so when you execute your loop and for each iteration you creates a new promise, you are creating new instances, and each one of those can be executed in their own time.



But what this even means? The explanation is, when you create 10 new Promises in a loop, each promise will be executed in his own time and probablly will mess up with your promise solving order.



What you can do to solve it? You can use await command to wait each promise to solve, like the code bellow:



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>

let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)

)

await p.then((message) =>
console.log(message)
).catch((message) =>
console.log(message)
)



Or you could try use Promise.all() which will basically solve the order for you, see the official docs here






share|improve this answer


















  • 1





    well, you can remove the .then if you're using await

    – pushkin
    Apr 17 at 19:45






  • 1





    Yes I could use async-await; and do prefer that. It's that I want to get to understand the promise.

    – Edwin
    Apr 17 at 19:49


















0














Because JavaScript are mono thread :



  • promise

  • eventListener

  • setTimeout

  • setInterval

previous listed method are not part of javascript enterpreter (V8 Engine for example), it delegate to the event loop which are part of browser or nodejs. more information here



Basically this code are delegate to 3th party (node, browser) which will decide himself when and on which order this collection of microtasks will be executed and return to the main thread.



is Why Following code :






 let p = new Promise((resolve, reject) => 
resolve('micro task thread');
);

p.then((message) =>
console.log(message)
).catch((message) =>
console.log(message)
);
console.log('main thread');





will print "main thread" then "micro task thread" but you don't have any obvious delayed code. Is because all main thread function call will be execute before doing task on eventLoop.



Most of the time, event loop will execute the collection as first come first rendered.






share|improve this answer























  • @Edwin i have not understand what you try to say. Ludovico post interesting answer. And my answer contain, i think, some tips to understand how async traitment work under the hood.

    – Yanis-git
    Apr 17 at 19:57











  • Fair question. Yes you gave a good explanation of how the event loop works and how promise fits in there. Ludvico posted a solution that produced the expected result.That still did not explain to me enough why it was happening. The key to understanding this was at MDN saying: The catch() is calling Promise.prototype.then(undefined, onrejected). Then I looked at the description of then Promise.prototype.then(). Under the syntax header I found this.

    – Edwin
    Apr 18 at 5:20











  • you can see much mind blown with following case : all case posted here :o

    – Yanis-git
    Apr 18 at 5:37


















0














I did found a solution here:
MDN promise then



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>
let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)

)

p.then((message) =>
console.log(message)
, failed =>
console.log(failed)
)



promise.catch() is calling promise.then(undefined, onreject). That is why resolve allways appeared first.






share|improve this answer

























  • I will note that though this is absolutely valid, most developers will never wrote code like that (and some would probably be confused as to it's behavior).

    – jhpratt
    Apr 17 at 20:06











Your Answer






StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55734046%2fwhy-does-the-resolve-message-appear-first%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























4 Answers
4






active

oldest

votes








4 Answers
4






active

oldest

votes









active

oldest

votes






active

oldest

votes









4














You can see what's going on under the hood by using your the console of your browser's dev tools and, possibly, setting break points (this articles might be helpful if u're using Chrome or Firefox):



enter image description here



As you can see, all your 10 promises are created before any of them are executed (resolve/reject).



Interestingly, in your code the resolved promises are handled first.



If you define the handlers in two separate definitions, you'll get the expected results:



p.then((message) => 
console.log(message)
)
p.catch((message) =>
console.log(message)
)


Output:



enter image description here






share|improve this answer























  • i am so surprize by the conclusion of your answer. I never imagined than chain vs multiple instruction can have this huge impact. Really good sharing

    – Yanis-git
    Apr 17 at 19:55















4














You can see what's going on under the hood by using your the console of your browser's dev tools and, possibly, setting break points (this articles might be helpful if u're using Chrome or Firefox):



enter image description here



As you can see, all your 10 promises are created before any of them are executed (resolve/reject).



Interestingly, in your code the resolved promises are handled first.



If you define the handlers in two separate definitions, you'll get the expected results:



p.then((message) => 
console.log(message)
)
p.catch((message) =>
console.log(message)
)


Output:



enter image description here






share|improve this answer























  • i am so surprize by the conclusion of your answer. I never imagined than chain vs multiple instruction can have this huge impact. Really good sharing

    – Yanis-git
    Apr 17 at 19:55













4












4








4







You can see what's going on under the hood by using your the console of your browser's dev tools and, possibly, setting break points (this articles might be helpful if u're using Chrome or Firefox):



enter image description here



As you can see, all your 10 promises are created before any of them are executed (resolve/reject).



Interestingly, in your code the resolved promises are handled first.



If you define the handlers in two separate definitions, you'll get the expected results:



p.then((message) => 
console.log(message)
)
p.catch((message) =>
console.log(message)
)


Output:



enter image description here






share|improve this answer













You can see what's going on under the hood by using your the console of your browser's dev tools and, possibly, setting break points (this articles might be helpful if u're using Chrome or Firefox):



enter image description here



As you can see, all your 10 promises are created before any of them are executed (resolve/reject).



Interestingly, in your code the resolved promises are handled first.



If you define the handlers in two separate definitions, you'll get the expected results:



p.then((message) => 
console.log(message)
)
p.catch((message) =>
console.log(message)
)


Output:



enter image description here







share|improve this answer












share|improve this answer



share|improve this answer










answered Apr 17 at 19:33









ludovicoludovico

1659




1659












  • i am so surprize by the conclusion of your answer. I never imagined than chain vs multiple instruction can have this huge impact. Really good sharing

    – Yanis-git
    Apr 17 at 19:55

















  • i am so surprize by the conclusion of your answer. I never imagined than chain vs multiple instruction can have this huge impact. Really good sharing

    – Yanis-git
    Apr 17 at 19:55
















i am so surprize by the conclusion of your answer. I never imagined than chain vs multiple instruction can have this huge impact. Really good sharing

– Yanis-git
Apr 17 at 19:55





i am so surprize by the conclusion of your answer. I never imagined than chain vs multiple instruction can have this huge impact. Really good sharing

– Yanis-git
Apr 17 at 19:55













2














The point is, Promises are made to be used as Asynchronous calls, so when you execute your loop and for each iteration you creates a new promise, you are creating new instances, and each one of those can be executed in their own time.



But what this even means? The explanation is, when you create 10 new Promises in a loop, each promise will be executed in his own time and probablly will mess up with your promise solving order.



What you can do to solve it? You can use await command to wait each promise to solve, like the code bellow:



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>

let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)

)

await p.then((message) =>
console.log(message)
).catch((message) =>
console.log(message)
)



Or you could try use Promise.all() which will basically solve the order for you, see the official docs here






share|improve this answer


















  • 1





    well, you can remove the .then if you're using await

    – pushkin
    Apr 17 at 19:45






  • 1





    Yes I could use async-await; and do prefer that. It's that I want to get to understand the promise.

    – Edwin
    Apr 17 at 19:49















2














The point is, Promises are made to be used as Asynchronous calls, so when you execute your loop and for each iteration you creates a new promise, you are creating new instances, and each one of those can be executed in their own time.



But what this even means? The explanation is, when you create 10 new Promises in a loop, each promise will be executed in his own time and probablly will mess up with your promise solving order.



What you can do to solve it? You can use await command to wait each promise to solve, like the code bellow:



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>

let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)

)

await p.then((message) =>
console.log(message)
).catch((message) =>
console.log(message)
)



Or you could try use Promise.all() which will basically solve the order for you, see the official docs here






share|improve this answer


















  • 1





    well, you can remove the .then if you're using await

    – pushkin
    Apr 17 at 19:45






  • 1





    Yes I could use async-await; and do prefer that. It's that I want to get to understand the promise.

    – Edwin
    Apr 17 at 19:49













2












2








2







The point is, Promises are made to be used as Asynchronous calls, so when you execute your loop and for each iteration you creates a new promise, you are creating new instances, and each one of those can be executed in their own time.



But what this even means? The explanation is, when you create 10 new Promises in a loop, each promise will be executed in his own time and probablly will mess up with your promise solving order.



What you can do to solve it? You can use await command to wait each promise to solve, like the code bellow:



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>

let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)

)

await p.then((message) =>
console.log(message)
).catch((message) =>
console.log(message)
)



Or you could try use Promise.all() which will basically solve the order for you, see the official docs here






share|improve this answer













The point is, Promises are made to be used as Asynchronous calls, so when you execute your loop and for each iteration you creates a new promise, you are creating new instances, and each one of those can be executed in their own time.



But what this even means? The explanation is, when you create 10 new Promises in a loop, each promise will be executed in his own time and probablly will mess up with your promise solving order.



What you can do to solve it? You can use await command to wait each promise to solve, like the code bellow:



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>

let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)

)

await p.then((message) =>
console.log(message)
).catch((message) =>
console.log(message)
)



Or you could try use Promise.all() which will basically solve the order for you, see the official docs here







share|improve this answer












share|improve this answer



share|improve this answer










answered Apr 17 at 19:33









Esdras XavierEsdras Xavier

45017




45017







  • 1





    well, you can remove the .then if you're using await

    – pushkin
    Apr 17 at 19:45






  • 1





    Yes I could use async-await; and do prefer that. It's that I want to get to understand the promise.

    – Edwin
    Apr 17 at 19:49












  • 1





    well, you can remove the .then if you're using await

    – pushkin
    Apr 17 at 19:45






  • 1





    Yes I could use async-await; and do prefer that. It's that I want to get to understand the promise.

    – Edwin
    Apr 17 at 19:49







1




1





well, you can remove the .then if you're using await

– pushkin
Apr 17 at 19:45





well, you can remove the .then if you're using await

– pushkin
Apr 17 at 19:45




1




1





Yes I could use async-await; and do prefer that. It's that I want to get to understand the promise.

– Edwin
Apr 17 at 19:49





Yes I could use async-await; and do prefer that. It's that I want to get to understand the promise.

– Edwin
Apr 17 at 19:49











0














Because JavaScript are mono thread :



  • promise

  • eventListener

  • setTimeout

  • setInterval

previous listed method are not part of javascript enterpreter (V8 Engine for example), it delegate to the event loop which are part of browser or nodejs. more information here



Basically this code are delegate to 3th party (node, browser) which will decide himself when and on which order this collection of microtasks will be executed and return to the main thread.



is Why Following code :






 let p = new Promise((resolve, reject) => 
resolve('micro task thread');
);

p.then((message) =>
console.log(message)
).catch((message) =>
console.log(message)
);
console.log('main thread');





will print "main thread" then "micro task thread" but you don't have any obvious delayed code. Is because all main thread function call will be execute before doing task on eventLoop.



Most of the time, event loop will execute the collection as first come first rendered.






share|improve this answer























  • @Edwin i have not understand what you try to say. Ludovico post interesting answer. And my answer contain, i think, some tips to understand how async traitment work under the hood.

    – Yanis-git
    Apr 17 at 19:57











  • Fair question. Yes you gave a good explanation of how the event loop works and how promise fits in there. Ludvico posted a solution that produced the expected result.That still did not explain to me enough why it was happening. The key to understanding this was at MDN saying: The catch() is calling Promise.prototype.then(undefined, onrejected). Then I looked at the description of then Promise.prototype.then(). Under the syntax header I found this.

    – Edwin
    Apr 18 at 5:20











  • you can see much mind blown with following case : all case posted here :o

    – Yanis-git
    Apr 18 at 5:37















0














Because JavaScript are mono thread :



  • promise

  • eventListener

  • setTimeout

  • setInterval

previous listed method are not part of javascript enterpreter (V8 Engine for example), it delegate to the event loop which are part of browser or nodejs. more information here



Basically this code are delegate to 3th party (node, browser) which will decide himself when and on which order this collection of microtasks will be executed and return to the main thread.



is Why Following code :






 let p = new Promise((resolve, reject) => 
resolve('micro task thread');
);

p.then((message) =>
console.log(message)
).catch((message) =>
console.log(message)
);
console.log('main thread');





will print "main thread" then "micro task thread" but you don't have any obvious delayed code. Is because all main thread function call will be execute before doing task on eventLoop.



Most of the time, event loop will execute the collection as first come first rendered.






share|improve this answer























  • @Edwin i have not understand what you try to say. Ludovico post interesting answer. And my answer contain, i think, some tips to understand how async traitment work under the hood.

    – Yanis-git
    Apr 17 at 19:57











  • Fair question. Yes you gave a good explanation of how the event loop works and how promise fits in there. Ludvico posted a solution that produced the expected result.That still did not explain to me enough why it was happening. The key to understanding this was at MDN saying: The catch() is calling Promise.prototype.then(undefined, onrejected). Then I looked at the description of then Promise.prototype.then(). Under the syntax header I found this.

    – Edwin
    Apr 18 at 5:20











  • you can see much mind blown with following case : all case posted here :o

    – Yanis-git
    Apr 18 at 5:37













0












0








0







Because JavaScript are mono thread :



  • promise

  • eventListener

  • setTimeout

  • setInterval

previous listed method are not part of javascript enterpreter (V8 Engine for example), it delegate to the event loop which are part of browser or nodejs. more information here



Basically this code are delegate to 3th party (node, browser) which will decide himself when and on which order this collection of microtasks will be executed and return to the main thread.



is Why Following code :






 let p = new Promise((resolve, reject) => 
resolve('micro task thread');
);

p.then((message) =>
console.log(message)
).catch((message) =>
console.log(message)
);
console.log('main thread');





will print "main thread" then "micro task thread" but you don't have any obvious delayed code. Is because all main thread function call will be execute before doing task on eventLoop.



Most of the time, event loop will execute the collection as first come first rendered.






share|improve this answer













Because JavaScript are mono thread :



  • promise

  • eventListener

  • setTimeout

  • setInterval

previous listed method are not part of javascript enterpreter (V8 Engine for example), it delegate to the event loop which are part of browser or nodejs. more information here



Basically this code are delegate to 3th party (node, browser) which will decide himself when and on which order this collection of microtasks will be executed and return to the main thread.



is Why Following code :






 let p = new Promise((resolve, reject) => 
resolve('micro task thread');
);

p.then((message) =>
console.log(message)
).catch((message) =>
console.log(message)
);
console.log('main thread');





will print "main thread" then "micro task thread" but you don't have any obvious delayed code. Is because all main thread function call will be execute before doing task on eventLoop.



Most of the time, event loop will execute the collection as first come first rendered.






 let p = new Promise((resolve, reject) => 
resolve('micro task thread');
);

p.then((message) =>
console.log(message)
).catch((message) =>
console.log(message)
);
console.log('main thread');





 let p = new Promise((resolve, reject) => 
resolve('micro task thread');
);

p.then((message) =>
console.log(message)
).catch((message) =>
console.log(message)
);
console.log('main thread');






share|improve this answer












share|improve this answer



share|improve this answer










answered Apr 17 at 19:47









Yanis-gitYanis-git

2,6571725




2,6571725












  • @Edwin i have not understand what you try to say. Ludovico post interesting answer. And my answer contain, i think, some tips to understand how async traitment work under the hood.

    – Yanis-git
    Apr 17 at 19:57











  • Fair question. Yes you gave a good explanation of how the event loop works and how promise fits in there. Ludvico posted a solution that produced the expected result.That still did not explain to me enough why it was happening. The key to understanding this was at MDN saying: The catch() is calling Promise.prototype.then(undefined, onrejected). Then I looked at the description of then Promise.prototype.then(). Under the syntax header I found this.

    – Edwin
    Apr 18 at 5:20











  • you can see much mind blown with following case : all case posted here :o

    – Yanis-git
    Apr 18 at 5:37

















  • @Edwin i have not understand what you try to say. Ludovico post interesting answer. And my answer contain, i think, some tips to understand how async traitment work under the hood.

    – Yanis-git
    Apr 17 at 19:57











  • Fair question. Yes you gave a good explanation of how the event loop works and how promise fits in there. Ludvico posted a solution that produced the expected result.That still did not explain to me enough why it was happening. The key to understanding this was at MDN saying: The catch() is calling Promise.prototype.then(undefined, onrejected). Then I looked at the description of then Promise.prototype.then(). Under the syntax header I found this.

    – Edwin
    Apr 18 at 5:20











  • you can see much mind blown with following case : all case posted here :o

    – Yanis-git
    Apr 18 at 5:37
















@Edwin i have not understand what you try to say. Ludovico post interesting answer. And my answer contain, i think, some tips to understand how async traitment work under the hood.

– Yanis-git
Apr 17 at 19:57





@Edwin i have not understand what you try to say. Ludovico post interesting answer. And my answer contain, i think, some tips to understand how async traitment work under the hood.

– Yanis-git
Apr 17 at 19:57













Fair question. Yes you gave a good explanation of how the event loop works and how promise fits in there. Ludvico posted a solution that produced the expected result.That still did not explain to me enough why it was happening. The key to understanding this was at MDN saying: The catch() is calling Promise.prototype.then(undefined, onrejected). Then I looked at the description of then Promise.prototype.then(). Under the syntax header I found this.

– Edwin
Apr 18 at 5:20





Fair question. Yes you gave a good explanation of how the event loop works and how promise fits in there. Ludvico posted a solution that produced the expected result.That still did not explain to me enough why it was happening. The key to understanding this was at MDN saying: The catch() is calling Promise.prototype.then(undefined, onrejected). Then I looked at the description of then Promise.prototype.then(). Under the syntax header I found this.

– Edwin
Apr 18 at 5:20













you can see much mind blown with following case : all case posted here :o

– Yanis-git
Apr 18 at 5:37





you can see much mind blown with following case : all case posted here :o

– Yanis-git
Apr 18 at 5:37











0














I did found a solution here:
MDN promise then



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>
let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)

)

p.then((message) =>
console.log(message)
, failed =>
console.log(failed)
)



promise.catch() is calling promise.then(undefined, onreject). That is why resolve allways appeared first.






share|improve this answer

























  • I will note that though this is absolutely valid, most developers will never wrote code like that (and some would probably be confused as to it's behavior).

    – jhpratt
    Apr 17 at 20:06















0














I did found a solution here:
MDN promise then



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>
let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)

)

p.then((message) =>
console.log(message)
, failed =>
console.log(failed)
)



promise.catch() is calling promise.then(undefined, onreject). That is why resolve allways appeared first.






share|improve this answer

























  • I will note that though this is absolutely valid, most developers will never wrote code like that (and some would probably be confused as to it's behavior).

    – jhpratt
    Apr 17 at 20:06













0












0








0







I did found a solution here:
MDN promise then



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>
let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)

)

p.then((message) =>
console.log(message)
, failed =>
console.log(failed)
)



promise.catch() is calling promise.then(undefined, onreject). That is why resolve allways appeared first.






share|improve this answer















I did found a solution here:
MDN promise then



for (let i = 0; i < 10; i++) 
let p = new Promise((resolve, reject) =>
let a = 1 + (i % 2)

if (a === 2)
resolve(i + ' resolve ' + a)
else
reject(i + ' reject ' + a)

)

p.then((message) =>
console.log(message)
, failed =>
console.log(failed)
)



promise.catch() is calling promise.then(undefined, onreject). That is why resolve allways appeared first.







share|improve this answer














share|improve this answer



share|improve this answer








edited Apr 18 at 6:07

























answered Apr 17 at 20:03









EdwinEdwin

685




685












  • I will note that though this is absolutely valid, most developers will never wrote code like that (and some would probably be confused as to it's behavior).

    – jhpratt
    Apr 17 at 20:06

















  • I will note that though this is absolutely valid, most developers will never wrote code like that (and some would probably be confused as to it's behavior).

    – jhpratt
    Apr 17 at 20:06
















I will note that though this is absolutely valid, most developers will never wrote code like that (and some would probably be confused as to it's behavior).

– jhpratt
Apr 17 at 20:06





I will note that though this is absolutely valid, most developers will never wrote code like that (and some would probably be confused as to it's behavior).

– jhpratt
Apr 17 at 20:06

















draft saved

draft discarded
















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55734046%2fwhy-does-the-resolve-message-appear-first%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Club Baloncesto Breogán Índice Historia | Pavillón | Nome | O Breogán na cultura popular | Xogadores | Adestradores | Presidentes | Palmarés | Historial | Líderes | Notas | Véxase tamén | Menú de navegacióncbbreogan.galCadroGuía oficial da ACB 2009-10, páxina 201Guía oficial ACB 1992, páxina 183. Editorial DB.É de 6.500 espectadores sentados axeitándose á última normativa"Estudiantes Junior, entre as mellores canteiras"o orixinalHemeroteca El Mundo Deportivo, 16 setembro de 1970, páxina 12Historia do BreogánAlfredo Pérez, o último canoneiroHistoria C.B. BreogánHemeroteca de El Mundo DeportivoJimmy Wright, norteamericano do Breogán deixará Lugo por ameazas de morteResultados de Breogán en 1986-87Resultados de Breogán en 1990-91Ficha de Velimir Perasović en acb.comResultados de Breogán en 1994-95Breogán arrasa al Barça. "El Mundo Deportivo", 27 de setembro de 1999, páxina 58CB Breogán - FC BarcelonaA FEB invita a participar nunha nova Liga EuropeaCharlie Bell na prensa estatalMáximos anotadores 2005Tempada 2005-06 : Tódolos Xogadores da Xornada""Non quero pensar nunha man negra, mais pregúntome que está a pasar""o orixinalRaúl López, orgulloso dos xogadores, presume da boa saúde económica do BreogánJulio González confirma que cesa como presidente del BreogánHomenaxe a Lisardo GómezA tempada do rexurdimento celesteEntrevista a Lisardo GómezEl COB dinamita el Pazo para forzar el quinto (69-73)Cafés Candelas, patrocinador del CB Breogán"Suso Lázare, novo presidente do Breogán"o orixinalCafés Candelas Breogán firma el mayor triunfo de la historiaEl Breogán realizará 17 homenajes por su cincuenta aniversario"O Breogán honra ao seu fundador e primeiro presidente"o orixinalMiguel Giao recibiu a homenaxe do PazoHomenaxe aos primeiros gladiadores celestesO home que nos amosa como ver o Breo co corazónTita Franco será homenaxeada polos #50anosdeBreoJulio Vila recibirá unha homenaxe in memoriam polos #50anosdeBreo"O Breogán homenaxeará aos seus aboados máis veteráns"Pechada ovación a «Capi» Sanmartín e Ricardo «Corazón de González»Homenaxe por décadas de informaciónPaco García volve ao Pazo con motivo do 50 aniversario"Resultados y clasificaciones""O Cafés Candelas Breogán, campión da Copa Princesa""O Cafés Candelas Breogán, equipo ACB"C.B. Breogán"Proxecto social"o orixinal"Centros asociados"o orixinalFicha en imdb.comMario Camus trata la recuperación del amor en 'La vieja música', su última película"Páxina web oficial""Club Baloncesto Breogán""C. B. Breogán S.A.D."eehttp://www.fegaba.com

Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020