How to console log big object in nodejs 11












0















In node.js 11 when I console.log big object it throws stack trace error, or logs full object with all inheritance.



I console.log dom object in jest test and receive error below, if I log small object all works fine.



error










share|improve this question

























  • If you want to check a large object, I think you should print obejct content to a text file, or using a debugger tool.

    – hoangdv
    Nov 13 '18 at 15:42













  • You could also look into converting your object to something that be streamed and then piping that stream to process.stdout

    – dpopp07
    Nov 13 '18 at 15:43
















0















In node.js 11 when I console.log big object it throws stack trace error, or logs full object with all inheritance.



I console.log dom object in jest test and receive error below, if I log small object all works fine.



error










share|improve this question

























  • If you want to check a large object, I think you should print obejct content to a text file, or using a debugger tool.

    – hoangdv
    Nov 13 '18 at 15:42













  • You could also look into converting your object to something that be streamed and then piping that stream to process.stdout

    – dpopp07
    Nov 13 '18 at 15:43














0












0








0








In node.js 11 when I console.log big object it throws stack trace error, or logs full object with all inheritance.



I console.log dom object in jest test and receive error below, if I log small object all works fine.



error










share|improve this question
















In node.js 11 when I console.log big object it throws stack trace error, or logs full object with all inheritance.



I console.log dom object in jest test and receive error below, if I log small object all works fine.



error







javascript node.js






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 13 '18 at 19:50









mihai

23.8k74068




23.8k74068










asked Nov 13 '18 at 14:52









Vitalii KhoteyVitalii Khotey

184




184













  • If you want to check a large object, I think you should print obejct content to a text file, or using a debugger tool.

    – hoangdv
    Nov 13 '18 at 15:42













  • You could also look into converting your object to something that be streamed and then piping that stream to process.stdout

    – dpopp07
    Nov 13 '18 at 15:43



















  • If you want to check a large object, I think you should print obejct content to a text file, or using a debugger tool.

    – hoangdv
    Nov 13 '18 at 15:42













  • You could also look into converting your object to something that be streamed and then piping that stream to process.stdout

    – dpopp07
    Nov 13 '18 at 15:43

















If you want to check a large object, I think you should print obejct content to a text file, or using a debugger tool.

– hoangdv
Nov 13 '18 at 15:42







If you want to check a large object, I think you should print obejct content to a text file, or using a debugger tool.

– hoangdv
Nov 13 '18 at 15:42















You could also look into converting your object to something that be streamed and then piping that stream to process.stdout

– dpopp07
Nov 13 '18 at 15:43





You could also look into converting your object to something that be streamed and then piping that stream to process.stdout

– dpopp07
Nov 13 '18 at 15:43












1 Answer
1






active

oldest

votes


















0














This tends to occur based on two cases,



1) When you have a limited memory set in your Node.js and when and execution requires more than that.



==> In situations like this, you can try increasing your memory limit like this (the following allocates 4GB memory) ,



node --max_old_space_size=4096 YOUR_SCRIPT.js


2) When your console.log tries to output a variable where it is getting manipulated asynchronously.



==> In situations like this, you can opt for this good library called console-sync which patches the traditional console.log and outputs the variable synchronously.



Hope this helps!






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%2f53283686%2fhow-to-console-log-big-object-in-nodejs-11%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    This tends to occur based on two cases,



    1) When you have a limited memory set in your Node.js and when and execution requires more than that.



    ==> In situations like this, you can try increasing your memory limit like this (the following allocates 4GB memory) ,



    node --max_old_space_size=4096 YOUR_SCRIPT.js


    2) When your console.log tries to output a variable where it is getting manipulated asynchronously.



    ==> In situations like this, you can opt for this good library called console-sync which patches the traditional console.log and outputs the variable synchronously.



    Hope this helps!






    share|improve this answer




























      0














      This tends to occur based on two cases,



      1) When you have a limited memory set in your Node.js and when and execution requires more than that.



      ==> In situations like this, you can try increasing your memory limit like this (the following allocates 4GB memory) ,



      node --max_old_space_size=4096 YOUR_SCRIPT.js


      2) When your console.log tries to output a variable where it is getting manipulated asynchronously.



      ==> In situations like this, you can opt for this good library called console-sync which patches the traditional console.log and outputs the variable synchronously.



      Hope this helps!






      share|improve this answer


























        0












        0








        0







        This tends to occur based on two cases,



        1) When you have a limited memory set in your Node.js and when and execution requires more than that.



        ==> In situations like this, you can try increasing your memory limit like this (the following allocates 4GB memory) ,



        node --max_old_space_size=4096 YOUR_SCRIPT.js


        2) When your console.log tries to output a variable where it is getting manipulated asynchronously.



        ==> In situations like this, you can opt for this good library called console-sync which patches the traditional console.log and outputs the variable synchronously.



        Hope this helps!






        share|improve this answer













        This tends to occur based on two cases,



        1) When you have a limited memory set in your Node.js and when and execution requires more than that.



        ==> In situations like this, you can try increasing your memory limit like this (the following allocates 4GB memory) ,



        node --max_old_space_size=4096 YOUR_SCRIPT.js


        2) When your console.log tries to output a variable where it is getting manipulated asynchronously.



        ==> In situations like this, you can opt for this good library called console-sync which patches the traditional console.log and outputs the variable synchronously.



        Hope this helps!







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 13 '18 at 15:39









        David RDavid R

        7,04942751




        7,04942751






























            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%2f53283686%2fhow-to-console-log-big-object-in-nodejs-11%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

            Florida Star v. B. J. F.

            Danny Elfman

            Retrieve a Users Dashboard in Tumblr with R and TumblR. Oauth Issues