await outside of async function doesn't throw error in console












8














MDN says:




Remember, the await keyword is only valid inside async functions. If you use it outside of an async function's body, you will get a SyntaxError.




But that's not true.



Try this code in DevTools console, no errors, just result:



async function a(val) { return val; }

await a(10) // await is not inside async function

10


What's wrong with the code or docs?






javascript asynchronous async-await console google-chrome-devtools







share|improve this question




















  • 1




    even just a simple await 10; prints 10
    – quirimmo
    4 hours ago










  • or await Promise.resolve(10)
    – Callam
    4 hours ago






  • 2




    it looks like has been supported since almost one year: chromium.googlesource.com/chromium/src.git/+/…
    – quirimmo
    4 hours ago






  • 1




    It works on root level, but you would always write functions in program and you cant use await without making the function async
    – Sumer
    4 hours ago
















8














MDN says:




Remember, the await keyword is only valid inside async functions. If you use it outside of an async function's body, you will get a SyntaxError.




But that's not true.



Try this code in DevTools console, no errors, just result:



async function a(val) { return val; }

await a(10) // await is not inside async function

10


What's wrong with the code or docs?






javascript asynchronous async-await console google-chrome-devtools







share|improve this question




















  • 1




    even just a simple await 10; prints 10
    – quirimmo
    4 hours ago










  • or await Promise.resolve(10)
    – Callam
    4 hours ago






  • 2




    it looks like has been supported since almost one year: chromium.googlesource.com/chromium/src.git/+/…
    – quirimmo
    4 hours ago






  • 1




    It works on root level, but you would always write functions in program and you cant use await without making the function async
    – Sumer
    4 hours ago














8












8








8


1





MDN says:




Remember, the await keyword is only valid inside async functions. If you use it outside of an async function's body, you will get a SyntaxError.




But that's not true.



Try this code in DevTools console, no errors, just result:



async function a(val) { return val; }

await a(10) // await is not inside async function

10


What's wrong with the code or docs?






javascript asynchronous async-await console google-chrome-devtools







share|improve this question















MDN says:




Remember, the await keyword is only valid inside async functions. If you use it outside of an async function's body, you will get a SyntaxError.




But that's not true.



Try this code in DevTools console, no errors, just result:



async function a(val) { return val; }

await a(10) // await is not inside async function

10


What's wrong with the code or docs?






javascript asynchronous async-await console google-chrome-devtools




javascript asynchronous async-await console google-chrome-devtools






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 1 hour ago









Bergi

362k57539863




362k57539863










asked 4 hours ago









Green

7,3573099170




7,3573099170








  • 1




    even just a simple await 10; prints 10
    – quirimmo
    4 hours ago










  • or await Promise.resolve(10)
    – Callam
    4 hours ago






  • 2




    it looks like has been supported since almost one year: chromium.googlesource.com/chromium/src.git/+/…
    – quirimmo
    4 hours ago






  • 1




    It works on root level, but you would always write functions in program and you cant use await without making the function async
    – Sumer
    4 hours ago














  • 1




    even just a simple await 10; prints 10
    – quirimmo
    4 hours ago










  • or await Promise.resolve(10)
    – Callam
    4 hours ago






  • 2




    it looks like has been supported since almost one year: chromium.googlesource.com/chromium/src.git/+/…
    – quirimmo
    4 hours ago






  • 1




    It works on root level, but you would always write functions in program and you cant use await without making the function async
    – Sumer
    4 hours ago








1




1




even just a simple await 10; prints 10
– quirimmo
4 hours ago




even just a simple await 10; prints 10
– quirimmo
4 hours ago












or await Promise.resolve(10)
– Callam
4 hours ago




or await Promise.resolve(10)
– Callam
4 hours ago




2




2




it looks like has been supported since almost one year: chromium.googlesource.com/chromium/src.git/+/…
– quirimmo
4 hours ago




it looks like has been supported since almost one year: chromium.googlesource.com/chromium/src.git/+/…
– quirimmo
4 hours ago




1




1




It works on root level, but you would always write functions in program and you cant use await without making the function async
– Sumer
4 hours ago




It works on root level, but you would always write functions in program and you cant use await without making the function async
– Sumer
4 hours ago












2 Answers
2






active

oldest

votes


















6














It looks like it has been supported since 11/08/2017:



https://chromium.googlesource.com/chromium/src.git/+/e8111c396fef38da6654093433b4be93bed01dce



If you spy the



ConsoleModel.js



at line 129, they have the function for evaluating expressions marked as async:



async evaluateCommandInConsole





share|improve this answer



















  • 1




    Nice detective work.
    – cgTag
    4 hours ago



















1














Nothing is wrong.



You've found a special feature of the DevTools console! It is there to make it as easy as possible to experiment with async-await code in a live environment. You can imagine that any code you enter in the console is wrapped in an async function automatically. In fact, as another answer pointed out, this is exactly what happens.



It's important to note that even though this works in the console, it is not a feature of JavaScript.



So, all of your observations are correct and expected! The MDN docs are accurate, because if you try to load a script on a page that uses await outside of an async function, it will error. On the other hand the DevTools console is designed to make this work (exclusively for developer ergonomics), so your code runs without any errors in the console.



This isn't the only trick the DevTools console has up its sleeve. In general if you really want to test how some code runs on a page, it's best to actually run the script on the page, not in the console.






share|improve this answer























    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%2f53905660%2fawait-outside-of-async-function-doesnt-throw-error-in-console%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    6














    It looks like it has been supported since 11/08/2017:



    https://chromium.googlesource.com/chromium/src.git/+/e8111c396fef38da6654093433b4be93bed01dce



    If you spy the



    ConsoleModel.js



    at line 129, they have the function for evaluating expressions marked as async:



    async evaluateCommandInConsole





    share|improve this answer



















    • 1




      Nice detective work.
      – cgTag
      4 hours ago
















    6














    It looks like it has been supported since 11/08/2017:



    https://chromium.googlesource.com/chromium/src.git/+/e8111c396fef38da6654093433b4be93bed01dce



    If you spy the



    ConsoleModel.js



    at line 129, they have the function for evaluating expressions marked as async:



    async evaluateCommandInConsole





    share|improve this answer



















    • 1




      Nice detective work.
      – cgTag
      4 hours ago














    6












    6








    6






    It looks like it has been supported since 11/08/2017:



    https://chromium.googlesource.com/chromium/src.git/+/e8111c396fef38da6654093433b4be93bed01dce



    If you spy the



    ConsoleModel.js



    at line 129, they have the function for evaluating expressions marked as async:



    async evaluateCommandInConsole





    share|improve this answer














    It looks like it has been supported since 11/08/2017:



    https://chromium.googlesource.com/chromium/src.git/+/e8111c396fef38da6654093433b4be93bed01dce



    If you spy the



    ConsoleModel.js



    at line 129, they have the function for evaluating expressions marked as async:



    async evaluateCommandInConsole






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited 4 hours ago

























    answered 4 hours ago









    quirimmo

    5,08611028




    5,08611028








    • 1




      Nice detective work.
      – cgTag
      4 hours ago














    • 1




      Nice detective work.
      – cgTag
      4 hours ago








    1




    1




    Nice detective work.
    – cgTag
    4 hours ago




    Nice detective work.
    – cgTag
    4 hours ago













    1














    Nothing is wrong.



    You've found a special feature of the DevTools console! It is there to make it as easy as possible to experiment with async-await code in a live environment. You can imagine that any code you enter in the console is wrapped in an async function automatically. In fact, as another answer pointed out, this is exactly what happens.



    It's important to note that even though this works in the console, it is not a feature of JavaScript.



    So, all of your observations are correct and expected! The MDN docs are accurate, because if you try to load a script on a page that uses await outside of an async function, it will error. On the other hand the DevTools console is designed to make this work (exclusively for developer ergonomics), so your code runs without any errors in the console.



    This isn't the only trick the DevTools console has up its sleeve. In general if you really want to test how some code runs on a page, it's best to actually run the script on the page, not in the console.






    share|improve this answer




























      1














      Nothing is wrong.



      You've found a special feature of the DevTools console! It is there to make it as easy as possible to experiment with async-await code in a live environment. You can imagine that any code you enter in the console is wrapped in an async function automatically. In fact, as another answer pointed out, this is exactly what happens.



      It's important to note that even though this works in the console, it is not a feature of JavaScript.



      So, all of your observations are correct and expected! The MDN docs are accurate, because if you try to load a script on a page that uses await outside of an async function, it will error. On the other hand the DevTools console is designed to make this work (exclusively for developer ergonomics), so your code runs without any errors in the console.



      This isn't the only trick the DevTools console has up its sleeve. In general if you really want to test how some code runs on a page, it's best to actually run the script on the page, not in the console.






      share|improve this answer


























        1












        1








        1






        Nothing is wrong.



        You've found a special feature of the DevTools console! It is there to make it as easy as possible to experiment with async-await code in a live environment. You can imagine that any code you enter in the console is wrapped in an async function automatically. In fact, as another answer pointed out, this is exactly what happens.



        It's important to note that even though this works in the console, it is not a feature of JavaScript.



        So, all of your observations are correct and expected! The MDN docs are accurate, because if you try to load a script on a page that uses await outside of an async function, it will error. On the other hand the DevTools console is designed to make this work (exclusively for developer ergonomics), so your code runs without any errors in the console.



        This isn't the only trick the DevTools console has up its sleeve. In general if you really want to test how some code runs on a page, it's best to actually run the script on the page, not in the console.






        share|improve this answer














        Nothing is wrong.



        You've found a special feature of the DevTools console! It is there to make it as easy as possible to experiment with async-await code in a live environment. You can imagine that any code you enter in the console is wrapped in an async function automatically. In fact, as another answer pointed out, this is exactly what happens.



        It's important to note that even though this works in the console, it is not a feature of JavaScript.



        So, all of your observations are correct and expected! The MDN docs are accurate, because if you try to load a script on a page that uses await outside of an async function, it will error. On the other hand the DevTools console is designed to make this work (exclusively for developer ergonomics), so your code runs without any errors in the console.



        This isn't the only trick the DevTools console has up its sleeve. In general if you really want to test how some code runs on a page, it's best to actually run the script on the page, not in the console.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 1 min ago









        Bergi

        362k57539863




        362k57539863










        answered 12 mins ago









        Caleb Miller

        2307




        2307






























            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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2f53905660%2fawait-outside-of-async-function-doesnt-throw-error-in-console%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

            Ottavio Pratesi

            Image
            .mw-parser-output .avviso .mbox-text-div>div,.mw-parser-output .avviso .mbox-text-full-div>div{font-size:90%}.mw-parser-output .avviso .mbox-image div{width:52px}.mw-parser-output .avviso .mbox-text-full-div .hide-when-compact{display:block} Questa voce sull'argomento ciclisti italiani è solo un abbozzo . Contribuisci a migliorarla secondo le convenzioni di Wikipedia. Ottavio Pratesi Nazionalità   Italia Ciclismo Specialità Strada Ritirato 1927 Carriera Squadre di club 1910-1911 Individuale 1912   Alcyon-Dunlop 1913 Globo-Dunlop 1914   Alcyon-Dunlop 1915-1922 Individuale 1923 Lygie 1924 Ostende 1925 Individuale   Modifica dati su Wikidata  · Manuale Ottavio Pratesi (Rosignano Marittimo, 1º gennaio 1889 – Livorno, 3 novembre 1977) è stato un ciclista su strada italiano, professionista tra il 1910 ed il 1925, era soprannominato il "Falco di ...
            Read more

            Tricia Helfer

            Image
            Tricia Helfer Tricia Helfer al Comic-Con 2015 Altezza 179 [1]  cm Misure 86-61-89 [1] Taglia 38 [1] (UE) - 8 [1] (US) Scarpe 40 [1] (UE) - 9 [1] (US) Occhi Azzurri [1] Capelli Biondo scuro [1] Modifica dati su Wikidata  · Manuale Tricia Helfer (Donalda, 11 aprile 1974) è una supermodella e attrice canadese, conosciuta principalmente per il suo ruolo di Numero Sei nella serie televisiva Battlestar Galactica . Indice 1 Carriera 2 Filmografia 2.1 Cinema 2.2 Televisione 2.3 Video musicali 2.4 Doppiatrice 2.4.1 Cinema 2.4.2 Televisione 2.4.3 Videogiochi 2.5 Produttrice 2.6 Agenzie 3 Doppiatrici italiane 4 Note 5 Altri progetti 6 Collegamenti esterni Carriera | Di origine inglese, tedesca, norvegese e svedese, nel 1992 Tricia vinse il concorso di "Ford Models Supermodel of the World", organizzato dall'agenzia Ford Models e fu poi assunta dall'agenzia ...
            Read more

            15 giugno

            Image
            gennaio  · febbraio  · marzo  · aprile  · maggio  · giugno 2018  · luglio  · agosto  · settembre  · ottobre  · novembre  · dicembre Ve Sa Do Lu Ma Me Gi Ve Sa Do Lu Ma Me Gi Ve Sa Do Lu Ma Me Gi Ve Sa Do Lu Ma Me Gi Ve Sa ← 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 → Il 15 giugno è il 166º giorno del calendario gregoriano (il 167º negli anni bisestili). Mancano 199 giorni alla fine dell'anno. Indice 1 Eventi 2 Nati 3 Morti 4 Feste e ricorrenze 4.1 Civili 4.2 Religiose 5 Altri progetti Eventi | 763 a.C. – Gli Assiri registrano un'eclissi solare 923 – Battaglia di Soissons: re Roberto I di Francia viene ucciso, re Carlo il Semplice viene arrestato dai sostenitori del duca Rodolfo di Borgogna 1094 – Reconquista: Valencia cade nelle mani di El Cid 1215 – Re Giovanni d'Inghilterra appone i...
            Read more