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












12














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
    Dec 23 at 17:27










  • or await Promise.resolve(10)
    – Callam
    Dec 23 at 17:34






  • 2




    it looks like has been supported since almost one year: chromium.googlesource.com/chromium/src.git/+/…
    – quirimmo
    Dec 23 at 17:37






  • 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
    Dec 23 at 17:47
















12














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
    Dec 23 at 17:27










  • or await Promise.resolve(10)
    – Callam
    Dec 23 at 17:34






  • 2




    it looks like has been supported since almost one year: chromium.googlesource.com/chromium/src.git/+/…
    – quirimmo
    Dec 23 at 17:37






  • 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
    Dec 23 at 17:47














12












12








12


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 Dec 23 at 20:52









Bergi

363k58540866




363k58540866










asked Dec 23 at 17:24









Green

7,38830100171




7,38830100171








  • 1




    even just a simple await 10; prints 10
    – quirimmo
    Dec 23 at 17:27










  • or await Promise.resolve(10)
    – Callam
    Dec 23 at 17:34






  • 2




    it looks like has been supported since almost one year: chromium.googlesource.com/chromium/src.git/+/…
    – quirimmo
    Dec 23 at 17:37






  • 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
    Dec 23 at 17:47














  • 1




    even just a simple await 10; prints 10
    – quirimmo
    Dec 23 at 17:27










  • or await Promise.resolve(10)
    – Callam
    Dec 23 at 17:34






  • 2




    it looks like has been supported since almost one year: chromium.googlesource.com/chromium/src.git/+/…
    – quirimmo
    Dec 23 at 17:37






  • 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
    Dec 23 at 17:47








1




1




even just a simple await 10; prints 10
– quirimmo
Dec 23 at 17:27




even just a simple await 10; prints 10
– quirimmo
Dec 23 at 17:27












or await Promise.resolve(10)
– Callam
Dec 23 at 17:34




or await Promise.resolve(10)
– Callam
Dec 23 at 17:34




2




2




it looks like has been supported since almost one year: chromium.googlesource.com/chromium/src.git/+/…
– quirimmo
Dec 23 at 17:37




it looks like has been supported since almost one year: chromium.googlesource.com/chromium/src.git/+/…
– quirimmo
Dec 23 at 17:37




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
Dec 23 at 17:47




It works on root level, but you would always write functions in program and you cant use await without making the function async
– Sumer
Dec 23 at 17:47












2 Answers
2






active

oldest

votes


















9














MDN docs is right and it explains how it works in JavaScript.



This is just a feature added by the DevTools for making you easier to test async/await code. And it is not a JavaScript feature.



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



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



















  • 2




    Nice detective work.
    – cgTag
    Dec 23 at 17:42



















7














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









    9














    MDN docs is right and it explains how it works in JavaScript.



    This is just a feature added by the DevTools for making you easier to test async/await code. And it is not a JavaScript feature.



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



    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



















    • 2




      Nice detective work.
      – cgTag
      Dec 23 at 17:42
















    9














    MDN docs is right and it explains how it works in JavaScript.



    This is just a feature added by the DevTools for making you easier to test async/await code. And it is not a JavaScript feature.



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



    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



















    • 2




      Nice detective work.
      – cgTag
      Dec 23 at 17:42














    9












    9








    9






    MDN docs is right and it explains how it works in JavaScript.



    This is just a feature added by the DevTools for making you easier to test async/await code. And it is not a JavaScript feature.



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



    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














    MDN docs is right and it explains how it works in JavaScript.



    This is just a feature added by the DevTools for making you easier to test async/await code. And it is not a JavaScript feature.



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



    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 Dec 24 at 13:12

























    answered Dec 23 at 17:41









    quirimmo

    5,26111129




    5,26111129








    • 2




      Nice detective work.
      – cgTag
      Dec 23 at 17:42














    • 2




      Nice detective work.
      – cgTag
      Dec 23 at 17:42








    2




    2




    Nice detective work.
    – cgTag
    Dec 23 at 17:42




    Nice detective work.
    – cgTag
    Dec 23 at 17:42













    7














    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




























      7














      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


























        7












        7








        7






        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 Dec 23 at 22:17









        Bergi

        363k58540866




        363k58540866










        answered Dec 23 at 22:06









        Caleb Miller

        3007




        3007






























            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

            Сан-Квентин

            Image
            Сан-Квентин Местоположение Сан-Квентин, Калифорния Координаты 37°56′13″ с. ш. 122°29′20″ з. д. H G Я O L Текущий статус Действует Режим безопасности минимальный и максимальный Количество мест 3 302 Открытие Июнь 1852 Находится в ведомстве California Department of Corrections and Rehabilitation Начальник Mike Martel, начальник  Сан-Квентин на Викискладе Сан-Квентин (англ.  San Quentin ) — тюрьма, располагающаяся на 432 акрах (около 1,7 км²), на мысе Сан-Квентин, в округе Марин, штат Калифорния, США. Тюрьма штата Калифорния Сан-Квентин была открыта в июле 1852 года и является старейшей в штате. Она была построена заключёнными, которые проживали в течение строительства на тюремном судне Вабан. В Сан-Квентине отбывали наказание и мужчины, и женщины до 1934 года, когда построили женскую тюрьму в Техачапи и туда перевели всех заключённых женщин. В Сан-Квентине приводятся в исполнение смертные казни, для этого имеется газовая камера, но...
            Read more

            8-я гвардейская общевойсковая армия

            Image
            8-я гвардейская общевойсковая ордена Ленина армия Награды: Войска: РККА → Советская армия → СВ России Род войск: Формирование: 1943 Расформирование (преобразование): 1992 Предшественник: 62-я армия (1942—43) → 8-я гвардейская общевойсковая армия (1943—92) → 8-й гвардейский армейский корпус (1992—98) Боевой путь Изюм-Барвенковская операция Донбасская операция Запорожская операция Битва за Днепр Днепропетровская операция Березнеговато-Снигирёвская операция Одесская операция Люблин-Брестская операция Варшавско-Познанская операция Восточно-Померанская операция Берлинская наступательная операция У этого термина существуют и другие значения, см. 8-я армия. Фотография Гвардейского Красного Знамени (лицевая сторона) 8-й гвардейской армии , образца 1943 года. Фотография Гвардейского Красного Знамени (оборотная сторона) 8-й гвардейской армии , образца 1943 года. 8-я гвардейская общевойсковая ордена Ленина армия  — гвардейское фор...
            Read more

            Алькесар

            Image
            Муниципалитет Алькесар Alquézar Герб 42°10′16″ с. ш. 0°01′27″ в. д. H G Я O L Страна Испания   Испания Автономное сообщество Арагон Провинция Уэска Комарка Сомонтано-де-Барбастро Алькальд Хосе Марияно Альтемир Ласкорс (ИСРП) История и география Площадь 32,36 км² Высота НУМ 660 м Часовой пояс UTC+1, летом UTC+2 Население Население 313 человек ( 2010 ) Плотность 9,92 чел./км² Этнохороним alquezarano/-a Цифровые идентификаторы Телефонный код +34 974 Почтовые индексы 22112 Автомобильный код HU alquezar.org   (исп.) Показать/скрыть карты Алькесар Алькесар Алькесар  Аудио, фото и видео на Викискладе Алькесар (исп.  Alquézar ) — муниципалитет в Испании, входит в провинцию Уэска, в составе автономного сообщества Арагон. Муниципалитет находится в составе района (комарки) Сомонтано-де-Барбастро. Занимает площадь 32,36 км². Население — 321 челове...
            Read more