Can't debug node.js using Chrome DevToolsHow do I debug Node.js applications?How do I get started with Node.jsWriting files in Node.jsHow do I pass command line arguments to a Node.js program?Read environment variables in Node.jsHow to decide when to use Node.js?How to exit in Node.jsWhat is the purpose of Node.js module.exports and how do you use it?Disabling Chrome cache for website developmentHow to restart Node application from Chrome Devtool

equation in minipage can't be numbered in the same line

What metal is most suitable for a ladder submerged in an underground water tank?

Is there any deeper thematic meaning to the white horse that Arya finds in The Bells (S08E05)?

Slice a list based on an index and items behind it in python

It is as easy as A B C, Figure out U V C from the given relationship

What is Feeblemind's effect on Ability Score Improvements?

Why did the soldiers of the North disobey Jon?

When is the AS keyword required?

To whom did Varys write those letters in Game of Thrones S8E5?

How to make a not so good looking person more appealing?

Single word that parallels "Recent" when discussing the near future

Can my American children re-enter the USA by International flight with a passport card? Being that their passport book has expired

What is the status of the Lannisters after Season 8 Episode 5, "The Bells"?

Will the volt, ampere, ohm or other electrical units change on May 20th, 2019?

How to not get blinded by an attack at dawn

Promotion comes with unexpected 24/7/365 on-call

Does addError() work outside of triggers?

How do I know which cipher suites can be disabled?

Capital gains on stocks sold to take initial investment off the table

The difference between きわめて and いたって

When did game consoles begin including FPUs?

the correct order of manual install WP and SSL on server

What dog breeds survive the apocalypse for generations?

How does Ctrl+c and Ctrl+v work?



Can't debug node.js using Chrome DevTools


How do I debug Node.js applications?How do I get started with Node.jsWriting files in Node.jsHow do I pass command line arguments to a Node.js program?Read environment variables in Node.jsHow to decide when to use Node.js?How to exit in Node.jsWhat is the purpose of Node.js module.exports and how do you use it?Disabling Chrome cache for website developmentHow to restart Node application from Chrome Devtool






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








1















When I run node --inspect app.js it says "Debugger attached". Then I open up chrome://inspect and I see my app running there so I click either Open dedicated DevTools or Inspect (next to the app's name). No matter how I open Node DevTools though, it just doesn't seem to be connected to anything (I can't see the source code there, the debugger statements are ignored, nothing logs to the console etc). I also tried opening it by opening regular DevTools and clicking the green Node icon.



It's weird because Chrome clearly sees the server running and something is clearly connecting to Node (and I don't think there's anything else on my network that could do that) but I still can't get DevTools to even acknowledge the server's existence.



I also distinctly remember debugging something the same exact way a few weeks ago and back then everything worked fine (although I remember I also struggled with this a bit but I somehow got it to work at the end, I think attaching the name of the file at the end of the command instead of in putting it in the middle did the trick at the end). The only thing that's happened since then is that I updated from v8 to v10 (LTS)



I've obviously tried rebooting and also reading every manual and article about node --inspect out there, nothing helped.










share|improve this question






















  • Maybe this can help you @M. Farnik medium.com/the-node-js-collection/…

    – arielb
    Mar 23 at 15:33











  • I've read that already and did exactly what it says, didn't help

    – M. Farnik
    Mar 23 at 15:50

















1















When I run node --inspect app.js it says "Debugger attached". Then I open up chrome://inspect and I see my app running there so I click either Open dedicated DevTools or Inspect (next to the app's name). No matter how I open Node DevTools though, it just doesn't seem to be connected to anything (I can't see the source code there, the debugger statements are ignored, nothing logs to the console etc). I also tried opening it by opening regular DevTools and clicking the green Node icon.



It's weird because Chrome clearly sees the server running and something is clearly connecting to Node (and I don't think there's anything else on my network that could do that) but I still can't get DevTools to even acknowledge the server's existence.



I also distinctly remember debugging something the same exact way a few weeks ago and back then everything worked fine (although I remember I also struggled with this a bit but I somehow got it to work at the end, I think attaching the name of the file at the end of the command instead of in putting it in the middle did the trick at the end). The only thing that's happened since then is that I updated from v8 to v10 (LTS)



I've obviously tried rebooting and also reading every manual and article about node --inspect out there, nothing helped.










share|improve this question






















  • Maybe this can help you @M. Farnik medium.com/the-node-js-collection/…

    – arielb
    Mar 23 at 15:33











  • I've read that already and did exactly what it says, didn't help

    – M. Farnik
    Mar 23 at 15:50













1












1








1








When I run node --inspect app.js it says "Debugger attached". Then I open up chrome://inspect and I see my app running there so I click either Open dedicated DevTools or Inspect (next to the app's name). No matter how I open Node DevTools though, it just doesn't seem to be connected to anything (I can't see the source code there, the debugger statements are ignored, nothing logs to the console etc). I also tried opening it by opening regular DevTools and clicking the green Node icon.



It's weird because Chrome clearly sees the server running and something is clearly connecting to Node (and I don't think there's anything else on my network that could do that) but I still can't get DevTools to even acknowledge the server's existence.



I also distinctly remember debugging something the same exact way a few weeks ago and back then everything worked fine (although I remember I also struggled with this a bit but I somehow got it to work at the end, I think attaching the name of the file at the end of the command instead of in putting it in the middle did the trick at the end). The only thing that's happened since then is that I updated from v8 to v10 (LTS)



I've obviously tried rebooting and also reading every manual and article about node --inspect out there, nothing helped.










share|improve this question














When I run node --inspect app.js it says "Debugger attached". Then I open up chrome://inspect and I see my app running there so I click either Open dedicated DevTools or Inspect (next to the app's name). No matter how I open Node DevTools though, it just doesn't seem to be connected to anything (I can't see the source code there, the debugger statements are ignored, nothing logs to the console etc). I also tried opening it by opening regular DevTools and clicking the green Node icon.



It's weird because Chrome clearly sees the server running and something is clearly connecting to Node (and I don't think there's anything else on my network that could do that) but I still can't get DevTools to even acknowledge the server's existence.



I also distinctly remember debugging something the same exact way a few weeks ago and back then everything worked fine (although I remember I also struggled with this a bit but I somehow got it to work at the end, I think attaching the name of the file at the end of the command instead of in putting it in the middle did the trick at the end). The only thing that's happened since then is that I updated from v8 to v10 (LTS)



I've obviously tried rebooting and also reading every manual and article about node --inspect out there, nothing helped.







node.js debugging google-chrome-devtools remote-debugging






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 23 at 15:11









M. FarnikM. Farnik

133




133












  • Maybe this can help you @M. Farnik medium.com/the-node-js-collection/…

    – arielb
    Mar 23 at 15:33











  • I've read that already and did exactly what it says, didn't help

    – M. Farnik
    Mar 23 at 15:50

















  • Maybe this can help you @M. Farnik medium.com/the-node-js-collection/…

    – arielb
    Mar 23 at 15:33











  • I've read that already and did exactly what it says, didn't help

    – M. Farnik
    Mar 23 at 15:50
















Maybe this can help you @M. Farnik medium.com/the-node-js-collection/…

– arielb
Mar 23 at 15:33





Maybe this can help you @M. Farnik medium.com/the-node-js-collection/…

– arielb
Mar 23 at 15:33













I've read that already and did exactly what it says, didn't help

– M. Farnik
Mar 23 at 15:50





I've read that already and did exactly what it says, didn't help

– M. Farnik
Mar 23 at 15:50












1 Answer
1






active

oldest

votes


















0














Seems to be a new chrome issue: https://github.com/nodejs/node/issues/26887






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%2f55315159%2fcant-debug-node-js-using-chrome-devtools%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














    Seems to be a new chrome issue: https://github.com/nodejs/node/issues/26887






    share|improve this answer



























      0














      Seems to be a new chrome issue: https://github.com/nodejs/node/issues/26887






      share|improve this answer

























        0












        0








        0







        Seems to be a new chrome issue: https://github.com/nodejs/node/issues/26887






        share|improve this answer













        Seems to be a new chrome issue: https://github.com/nodejs/node/issues/26887







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 26 at 20:30









        rambinorambino

        1




        1





























            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%2f55315159%2fcant-debug-node-js-using-chrome-devtools%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

            SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

            용인 삼성생명 블루밍스 목차 통계 역대 감독 선수단 응원단 경기장 같이 보기 외부 링크 둘러보기 메뉴samsungblueminx.comeh선수 명단용인 삼성생명 블루밍스용인 삼성생명 블루밍스ehsamsungblueminx.comeheheheh

            155 수학 과학 기타 둘러보기 메뉴eh추가해eh문서를 완성해