Why does the resolve message appear first? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 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

Why wasn't DOSKEY integrated with COMMAND.COM?

Do square wave exist?

8 Prisoners wearing hats

Irreducible of finite Krull dimension implies quasi-compact?

Is it ethical to give a final exam after the professor has quit before teaching the remaining chapters of the course?

Do jazz musicians improvise on the parent scale in addition to the chord-scales?

How to Make a Beautiful Stacked 3D Plot

Do wooden building fires get hotter than 600°C?

Is it cost-effective to upgrade an old-ish Giant Escape R3 commuter bike with entry-level branded parts (wheels, drivetrain)?

Compare a given version number in the form major.minor.build.patch and see if one is less than the other

Is there a kind of relay only consumes power when switching?

Why do we bend a book to keep it straight?

How do I make this wiring inside cabinet safer? (Pic)

Is it fair for a professor to grade us on the possession of past papers?

Extracting terms with certain heads in a function

Why does the resolve message appear first?

What do you call the main part of a joke?

Is there any way for the UK Prime Minister to make a motion directly dependent on Government confidence?

Why are the trig functions versine, haversine, exsecant, etc, rarely used in modern mathematics?

Does classifying an integer as a discrete log require it be part of a multiplicative group?

How do I find out the mythology and history of my Fortress?

Around usage results

For a new assistant professor in CS, how to build/manage a publication pipeline

How would a mousetrap for use in space work?



Why does the resolve message appear first?



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
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
    7 hours ago











  • You have 10 promises, they don't "go back to rejected" like you said.

    – Kev
    7 hours ago






  • 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
    7 hours ago






  • 2





    Yes Junvar. That is my question.

    – Edwin
    6 hours ago






  • 4





    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
    6 hours ago

















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
    7 hours ago











  • You have 10 promises, they don't "go back to rejected" like you said.

    – Kev
    7 hours ago






  • 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
    7 hours ago






  • 2





    Yes Junvar. That is my question.

    – Edwin
    6 hours ago






  • 4





    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
    6 hours ago













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 26 mins ago









Boann

37.5k1291123




37.5k1291123










asked 7 hours ago









EdwinEdwin

614




614







  • 3





    You are creating new promise on every iteration

    – brk
    7 hours ago











  • You have 10 promises, they don't "go back to rejected" like you said.

    – Kev
    7 hours ago






  • 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
    7 hours ago






  • 2





    Yes Junvar. That is my question.

    – Edwin
    6 hours ago






  • 4





    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
    6 hours ago












  • 3





    You are creating new promise on every iteration

    – brk
    7 hours ago











  • You have 10 promises, they don't "go back to rejected" like you said.

    – Kev
    7 hours ago






  • 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
    7 hours ago






  • 2





    Yes Junvar. That is my question.

    – Edwin
    6 hours ago






  • 4





    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
    6 hours ago







3




3





You are creating new promise on every iteration

– brk
7 hours ago





You are creating new promise on every iteration

– brk
7 hours ago













You have 10 promises, they don't "go back to rejected" like you said.

– Kev
7 hours ago





You have 10 promises, they don't "go back to rejected" like you said.

– Kev
7 hours ago




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
7 hours ago





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
7 hours ago




2




2





Yes Junvar. That is my question.

– Edwin
6 hours ago





Yes Junvar. That is my question.

– Edwin
6 hours ago




4




4





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
6 hours ago





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
6 hours ago












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
    5 hours ago


















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
    6 hours ago






  • 1





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

    – Edwin
    6 hours ago


















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
    5 hours ago


















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)
)






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
    5 hours ago











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
    5 hours ago















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
    5 hours ago













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 6 hours ago









ludovicoludovico

875




875












  • 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
    5 hours ago

















  • 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
    5 hours ago
















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
5 hours ago





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
5 hours ago













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
    6 hours ago






  • 1





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

    – Edwin
    6 hours ago















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
    6 hours ago






  • 1





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

    – Edwin
    6 hours ago













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 6 hours ago









Esdras XavierEsdras Xavier

45017




45017







  • 1





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

    – pushkin
    6 hours ago






  • 1





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

    – Edwin
    6 hours ago












  • 1





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

    – pushkin
    6 hours ago






  • 1





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

    – Edwin
    6 hours ago







1




1





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

– pushkin
6 hours ago





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

– pushkin
6 hours ago




1




1





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

– Edwin
6 hours ago





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

– Edwin
6 hours ago











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
    5 hours ago















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
    5 hours ago













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 6 hours ago









Yanis-gitYanis-git

2,6291725




2,6291725












  • @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
    5 hours ago

















  • @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
    5 hours ago
















@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
5 hours ago





@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
5 hours ago











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)
)






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
    5 hours ago















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)
)






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
    5 hours ago













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)
)






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)
)







share|improve this answer














share|improve this answer



share|improve this answer








edited 3 hours ago









pushkin

4,726113055




4,726113055










answered 5 hours ago









EdwinEdwin

614




614












  • 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
    5 hours ago

















  • 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
    5 hours ago
















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
5 hours ago





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
5 hours ago

















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

What does “fit” mean in this sentence? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)How does 'jealousy' mean 'suspicion'?What does “not so say” mean?Does “somebody of my caliber” mean the speaker themselves?“accounting for high fasting blood glucose”- help about the meaningWhat does “cloaked by NDA” mean in this context?What does it mean by 'community ownership' in this context?What does “human corroborators” mean in this context?What does “everything but a fire” mean in this context?What does “run” mean here?What does “rabbited” mean/imply in this sentence?

History of India Contents Prehistoric era (until c. 3300 BCE) Bronze Age – "First urbanisation" (c. 3300 – c. 1800 BCE) Climate change, de-urbanisation, and Indo-Aryan migrations (c.1800 – 1500 BCE) Iron Age - Vedic period (c. 1500 – c. 600 BCE) "Second urbanisation" (c. 600 – c. 200 BCE) Classical to early medieval periods (c. 200 BCE – c. 1200 CE) Late medieval period (c. 1200 – 1526 CE) Early modern period (c. 1526–1858 CE) Modern period and independence (after c. 1850 CE) Historiography See also References Further reading External links Navigation menureviewedee[update]The crisisThe Evolution and History of Human Populations in South Asia: Inter-disciplinary Studies in Archaeology, Biological Anthropology, Linguistics and GeneticsThe Ancient Indus: Urbanism, Economy, and Society"Indus River Valley Civilizations"The Ancient Indus: Urbanism, Economy, and Society"India before the British: The Mughal Empire and its Rivals, 1526–1857"Why Europe Grew Rich and Asia Did Not: Global Economic Divergence, 1600–1850Development Centre Studies The World Economy Historical Statistics: Historical StatisticsDeveloping cultures: case studiesEthnic Groups of South Asia and the Pacific: An Encyclopedia: An Encyclopedia"Indian Economy During British Rule""Economic Impact of the British Rule in India | Indian History"The Bone Readers: Science and Politics in Human Origins Research"Out of Africa: new hypotheses and evidence for the dispersal of Homo sapiens along the Indian Ocean rim"10.3109/0301446100363924920334598"Genetic and archaeological perspectives on the initial modern human colonization of southern Asia"2013PNAS..11010699M10.1073/pnas.1306043110369678523754394"Edakkal Caves|Places Around in Wayanad"Protecting megaliths to keep history alive The Hindu daily"Archaeologists rock solid behind Edakkal Cave"The Global Prehistory of Human Migration"Indus Valley 2,000 years older than thought"the original"Stepwells -Cosmology of Subterranean Architecture as seen in Adalaj"A History of Ancient and Early medieval India : from the Stone Age to the 12th century"Stone celts in Harappa"the original"Peoples and languages in pre-islamic Indus valley"the original"The Sindhi language"the originalThe Aryan chromosome"Fluvial landscapes of the Harappan Civilization"2012PNAS..109E1688G10.1073/pnas.1112743109338705422645375"Is River Ghaggar, Saraswati? Geochemical Constraints""An Ancient Civilization, Upended by Climate Change""Huge Ancient Civilization's Collapse Explained"2003GeoRL..30.1425S10.1029/2002GL0168222006QSRv...25.1283M10.1016/j.quascirev.2005.10.0122011QuInt.229..140M10.1016/j.quaint.2009.11.012Climate Change and the Course of Global History: A Rough JourneyA History of Ancient and Early Medieval India: From the Stone Age to the 12th CenturyA History of Ancient and Mediaeval India: From the Stone Age to the 12th CenturyAntennae SwordA History of IndiaA History of IndiaAn Introduction to Hinduism"India: The Late 2nd Millennium and the Reemergence of Urbanism"The Coinage of Ancient IndiaA Sanskrit reader: with vocabulary and notesPedigree: the origins of words from nature"Early Sanskritization. Origins and Development of the Kuru State"10.11588/ejvs.1995.4.823The Sanskrit epics, Part 2The City in South AsiaThe UpanishadsAn Introduction to HinduismReligions of the World, Second Edition: A Comprehensive Encyclopedia of Beliefs and PracticesA History of Ancient and Early Medieval India: From the Stone Age to the 12th CenturyEarly India: From the Origins to AD 1300Republics in ancient Indiapp. 83ff"Magadha Empire""Lumbini Development Trust: Restoring the Lumbini Garden"the originalThe great armies of antiquityarchived"The Achaemenid Persian Empire (550–330 B.C.)""East–West Orientation of Historical Empires"1076-156X"Dinner on the Grand Trunk Road"10.2307/32502263250226"Silappathikaram Tamil Literature"the originalManimekalai – English transliteration of Tamil originalIndian Temple Architecture: Form and Transformation : the Karṇāṭa Drāviḍa Tradition, 7th to 13th CenturiesBuddhist ArchitectureA History of India"The World Economy (GDP) : Historical Statistics by Professor Angus Maddison"The World Economy – Volume 1: A Millennial Perspective and Volume 2: Historical Statistics10.2307/32502140004-36483250214A Comprehensive History of India: Volume 2Between the Empires: Society in India, 300 to 400Emergence of Viṣṇu and Śiva Images in India: Numismatic and Sculptural Evidence"Parthian Pair of Earrings"the originalThe Medical Times and Gazette, Volume 1Greatest emporium in the worldThe Cambridge History of Ancient China: From the Origins of Civilization to 221 BCBuddhist Records of the Western WorldArchaeology in Soviet Central AsiaThe Grandeur of Gandhara: The Ancient Buddhist Civilization of the Swat, Peshawar, Kabul and Indus ValleysIndian Sculpture: Circa 500 B.C.-A.D. 700"The History of Pakistan: The Kushans"Gupta Dynasty – MSN Encartathe original"India – Historical Setting – The Classical Age – Gupta and Harsha""Gupta Dynasty, Golden Age Of India"the original"The Age of the Guptas and After"the originalNumber Theory and Its History"Gupta dynasty (Indian dynasty)""Gupta dynasty: empire in 4th century"the original"The Story of India – Photo Gallery"The ASI say499315420"Pallava script"p. 145"CNG: eAuction 329. INDIA, Post-Gupta (Ganges Valley). Vardhanas of Thanesar and Kanauj. Harshavardhana. Circa AD 606–647. AR Drachm (13mm, 2.28 g, 1h)""Harsha""Sthanvishvara (historical region, India)""Harsha (Indian emperor)"Shyama Kumar Chattopadhyaya (2000) The Philosophy of Sankar's Advaita VedantaShankara's IntroductionShankara's Introduction19373677Shankara's IntroductionIs The Buddhist 'No-Self' Doctrine Compatible With Pursuing Nirvana?The Seven Spiritual Laws Of YogaIndia: The Ancient Past. A History of the Indian-Subcontinent from 7000 BC to AD 1200The Kashmir Series: Glimpses of Kashmiri Culture – Vivekananda Kendra, Kanyakumari (p. 57).Al-Hind: Early Medieval India and the Expansion of Islam, 7th–11th CenturiesHistory of GopāchalaLand of Two Rivers: A History of Bengal from the Mahabharata to MujibEuropean Trade and Colonial ConquestA History of IndiaA Comprehensive History Of Ancient India (3 Vol. Set)"The Last Years of Cholas: The decline and fall of a dynasty"the originalFascinating Hindutva: Saffron Politics and Dalit MobilisationGazetteer of the province of OudhAl- Hind: The slave kings and the Islamic conquest. 2"Shahi Family"The Cambridge history of Islam"Ameer Nasir-ood-deen Subooktugeen"Gazetteer of the Attock District, 1930, Part 1Land of seven rivers: History of India's GeographyTemple Desecration and Indo-Muslim StatesIslam in South Asia: A Short HistoryBeyond Orientalism: The Work of Wilhelm Halbfass and Its Impact on Indian and Cross-cultural StudiesThe Making of Terrorism in Pakistan: Historical and Social Roots of ExtremismOrnament in Indian ArchitectureA historical review of Hindu India: 300 B.C. to 1200 A.D."Indian States and Union Territories"Islam in South Asia: A Short HistoryA Brief History of the Indian PeoplesThe Modern ReviewDelhi Sultanate"Battuta's Travels: Delhi, capital of Muslim India"the original"Timur – conquest of India"the originalIndia HandbookBhaktiThe Four Denomination of Hinduism10.1007/s11407-008-9049-925691067"Vijayanagara Research Project::Elephant Stables"10.2307/26465262646526Historical Dictionary of the TamilsBihar General Knowledge DigestMapping Bihar: From Medieval to Modern TimesPopular Literature and Pre-modern Societies in South AsiaA manual of the Kistna district in the presidency of MadrasAncient Indian History and CivilizationFragmented Memories: Struggling to be Tai-Ahom in India"The Islamic World to 1600: Rise of the Great Islamic Empires (The Mughal Empire)"the originalDynasties: A Global History of Power, 1300–1800, p. 105"Whose fort is it anyway"10.1111/0020-8833.000532600793Development Centre Studies The World Economy Historical Statistics: Historical Statistics"India's Deindustrialization in the 18th and 19th Centuries"The Mughal Empire, p. 190"The Long Globalization and Textile Producers in India"The Mughal World: Life in India's Last Golden AgeAurangzeb: The Life and Legacy of India's Most Controversial KingIn the Shadow of the Taj: A Portrait of Agra"Iran in the Age of the Raj"p. 8610.2307/20539802053980Delhi, the Capital of IndiaAn Advanced History of Modern India"Journal of the Tanjore Maharaja Serfoji's Sarasvati Mahal Library"The Rediscovery of India: A New SubcontinentIslamic Renaissance In South Asia (1707–1867) : The Role Of Shah Waliallah & His SuccessorsAn Advanced History of Modern IndiaThe Great Maratha Mahadaji Scindia"Full text of "Selections from the papers of Lord Metcalfe; late governor-general of India, governor of Jamaica, and governor-general of Canada""The Discovery Of IndiaThe Sacred City of the Hindus: An Account of Benares in Ancient and Modern TimesResurrecting Banaras: Urban Space, Architecture and Religious BoundariesFaith & Philosophy of Sikhism"Missiles mainstay of Pak's N-arsenal"History Modern India By S.N. Sen"Sirajuddaula"ArchivedLongman History & Civics (Dual Government in Bengal)Madhya Pradesh National Means-Cum-Merit Scholarship Exam (Warren Hasting's system of Dual Government)A Military History of Britain: from 1775 to the PresentIndian Cultural Heritage Perspective For TourismHindu Rulers, Muslim Subjects: Islam, Rights, and the History of KashmirIndian HistoryAn Atlas and Survey of South Asian HistoryAn Historical Account of the British Trade Over the Caspian SeaIndian Merchants and Eurasian Trade, 1600–1750The Indian diaspora in Central Asia and its trade, 1550–1900From Constantinople to the home of Omar Khayyam: travels in Transcaucasia and northern Persia for historic and literary researchA journey from Bengal to England: through the northern part of India, Kashmire, Afghanistan, and Persia, and into Russia, by the Caspian-SeaA Second Journey through Persia, Armenia, and Asia Minor, to Constantinople, between the Years 1810 and 1816Reports from the consuls of the United States, 1887Portugal and its Empire, 1250–1800 (Collected Essays in Memory of Glenn J. Ames).: Portuguese Studies Review, Vol. 17, No. 1The Dutch Power in Kerala, 1729–1758http://mod.nic.inArchivedDossier Goa – A Recusa do Sacrifício InútilAn Imperial Crisis in British India: The Manipur Uprising of 1891The Truth of Babri Mosque"Kolkata (Calcutta) : History"the original"Robert Clive, Baron Clive, 'Clive of India', 1725–1774""The Transformation from a Pre-Colonial to a Colonial Order: The Case of India"10.2307/25955872595587A versatile geniusArchived10.1109/MWSYM.1997.602854"Rabindranath Tagore on Education"the original"Essay on 'Derozio and the Young Bengal Movement'"Poverty and Famines: An Essay on Entitlement and Deprivation"Plague"the originalPopulation Growth and Land Use"Reintegrating India with the World Economy""Census Of India 1931"A history of modern India, 1480–1950"'India's well-timed diversification of army helped democracy' | Business Standard News"Bal Gangadhar Tilak: Struggle for Swaraj"Participants from the Indian subcontinent in the First World War""Commonwealth War Graves Commission Annual Report 2007–2008 Online"the original1462689197110.1017/s0010417500016534178920Eurocentrism: a marxian critical realist critique"Ranjit Guha, "On Some Aspects of Historiography of Colonial India""10.2307/2168385216838510.7202/016593ar"Harvard scholar says the idea of India dates to a much earlier time than the British or the Mughals""In The Footsteps of Pilgrims""India's spiritual landscape: The heavens and the earth""India: A Sacred Geography by Diana L Eck – review"Modern India: The Origins of an Asian Democracy10.2307/21694222169422964322464"The Indian Subcontinent and 'Out of Africa 1'"254043308Encyclopedia of World ReligionsThe Evolution and History of Human Populations in South Asia: Inter-disciplinary Studies in Archaeology, Biological Anthropology, Linguistics and Genetics"The Early Paleolithic of the Indian Subcontinent: Hominin Colonization, Dispersals and Occupation History"Ancient Indian History and CivilizationAncient Indian Social History: Some Interpretationsthe originalIndia Before EuropeA Concise History of Modern India"The beginning of the historical period, c. 500–150 BCE"full textA History of Indiathe originalexcerpt and text searchexcerptexcerptAn Economic History of India: From Pre-Colonial Times to 1991excerpt and text searchexcerpt and text searchIndia as known to the ancient world10.1111/j.1468-0289.1985.tb00391.x2597191onlineThe History of India, as told by its own historians. The Muhammadan Periodonline editionHans William Brown research collection on 19th-century missionary work in India, 1882–1932, Ms. Coll. 1033, Kislak Center for Special Collections, Rare Books and Manuscripts, University of Pennsylvaniaee

Isurus Índice Especies | Notas | Véxase tamén | Menú de navegación"A compendium of fossil marine animal genera (Chondrichthyes entry)"o orixinal"A review of the Tertiary fossil Cetacea (Mammalia) localities in wales port taf Museum Victoria"o orixinalThe Vertebrate Fauna of the Selma Formation of Alabama. Part VII. Part VIII. The Mosasaurs The Fishes50419737IDsh85068767Isurus2548834613242066569678159923NHMSYS00210535017845105743