Cannot enable debugger for Nodejs VSCODEHow can I update NodeJS and NPM to the next versions?How do I resolve “Cannot find module” error using Node.js?toggleBreakpointsTargetFactory specified id is already registereddebugging a Nodejs application listening on a porthow to debug javascript in nodejs on Windows when I'm not the caller of node.exeNew Node V8 Inspector not logging to console on Windows PCDebugging NodeJs Program in Docker Container with VSCode in one stepUsing an old version of node in VS Code debuggerVSCode - debugger not hitting break-point on postman requestDebugging NodeJS child process' VSCode babel-node

Why are electrically insulating heatsinks so rare? Is it just cost?

Show that if two triangles built on parallel lines, with equal bases have the same perimeter only if they are congruent.

Writing rule stating superpower from different root cause is bad writing

How can bays and straits be determined in a procedurally generated map?

Font hinting is lost in Chrome-like browsers (for some languages )

Can a Warlock become Neutral Good?

Languages that we cannot (dis)prove to be Context-Free

Can divisibility rules for digits be generalized to sum of digits

Which models of the Boeing 737 are still in production?

Why not use SQL instead of GraphQL?

What does "Puller Prush Person" mean?

What does it mean to describe someone as a butt steak?

Why can't I see bouncing of a switch on an oscilloscope?

Why doesn't Newton's third law mean a person bounces back to where they started when they hit the ground?

Why do I get two different answers for this counting problem?

Test whether all array elements are factors of a number

What typically incentivizes a professor to change jobs to a lower ranking university?

A newer friend of my brother's gave him a load of baseball cards that are supposedly extremely valuable. Is this a scam?

Email Account under attack (really) - anything I can do?

TGV timetables / schedules?

Python: next in for loop

How old can references or sources in a thesis be?

"to be prejudice towards/against someone" vs "to be prejudiced against/towards someone"

What is the word for reserving something for yourself before others do?



Cannot enable debugger for Nodejs VSCODE


How can I update NodeJS and NPM to the next versions?How do I resolve “Cannot find module” error using Node.js?toggleBreakpointsTargetFactory specified id is already registereddebugging a Nodejs application listening on a porthow to debug javascript in nodejs on Windows when I'm not the caller of node.exeNew Node V8 Inspector not logging to console on Windows PCDebugging NodeJs Program in Docker Container with VSCode in one stepUsing an old version of node in VS Code debuggerVSCode - debugger not hitting break-point on postman requestDebugging NodeJS child process' VSCode babel-node






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








0















This is my first time trying to setup Nodejs with debugger tool. My lauch.json code is:




// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [

"type": "node",
"request": "launch",
"name": "Launch Program",
"program": "$workspaceFolder/app.js"
,

"type": "node",
"request": "attach",
"name": "Attach by Process ID",
"processId": "$command:PickProcess"

]



When I run the debugger in VS code and go to debug console. I get:




C:Program Filesnodejsnode.exe --inspect-brk=29182 app.js

Debugger
listening on ws://127.0.0.1:29182/c2a39cf7-ab13-4sd1b-afs5-eb9wqwq5de9




I have setup a breakpoint on my app.js as well.



I have tried to go to the



ws://127.0.0.1:29182/c2a39cf7-ab13-4sd1b-afs5-eb9wqwq5de9


url as shown in the debugger but it give me:




Site cannot be reached




error in chrome










share|improve this question




























    0















    This is my first time trying to setup Nodejs with debugger tool. My lauch.json code is:




    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [

    "type": "node",
    "request": "launch",
    "name": "Launch Program",
    "program": "$workspaceFolder/app.js"
    ,

    "type": "node",
    "request": "attach",
    "name": "Attach by Process ID",
    "processId": "$command:PickProcess"

    ]



    When I run the debugger in VS code and go to debug console. I get:




    C:Program Filesnodejsnode.exe --inspect-brk=29182 app.js

    Debugger
    listening on ws://127.0.0.1:29182/c2a39cf7-ab13-4sd1b-afs5-eb9wqwq5de9




    I have setup a breakpoint on my app.js as well.



    I have tried to go to the



    ws://127.0.0.1:29182/c2a39cf7-ab13-4sd1b-afs5-eb9wqwq5de9


    url as shown in the debugger but it give me:




    Site cannot be reached




    error in chrome










    share|improve this question
























      0












      0








      0








      This is my first time trying to setup Nodejs with debugger tool. My lauch.json code is:




      // Use IntelliSense to learn about possible attributes.
      // Hover to view descriptions of existing attributes.
      // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
      "version": "0.2.0",
      "configurations": [

      "type": "node",
      "request": "launch",
      "name": "Launch Program",
      "program": "$workspaceFolder/app.js"
      ,

      "type": "node",
      "request": "attach",
      "name": "Attach by Process ID",
      "processId": "$command:PickProcess"

      ]



      When I run the debugger in VS code and go to debug console. I get:




      C:Program Filesnodejsnode.exe --inspect-brk=29182 app.js

      Debugger
      listening on ws://127.0.0.1:29182/c2a39cf7-ab13-4sd1b-afs5-eb9wqwq5de9




      I have setup a breakpoint on my app.js as well.



      I have tried to go to the



      ws://127.0.0.1:29182/c2a39cf7-ab13-4sd1b-afs5-eb9wqwq5de9


      url as shown in the debugger but it give me:




      Site cannot be reached




      error in chrome










      share|improve this question














      This is my first time trying to setup Nodejs with debugger tool. My lauch.json code is:




      // Use IntelliSense to learn about possible attributes.
      // Hover to view descriptions of existing attributes.
      // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
      "version": "0.2.0",
      "configurations": [

      "type": "node",
      "request": "launch",
      "name": "Launch Program",
      "program": "$workspaceFolder/app.js"
      ,

      "type": "node",
      "request": "attach",
      "name": "Attach by Process ID",
      "processId": "$command:PickProcess"

      ]



      When I run the debugger in VS code and go to debug console. I get:




      C:Program Filesnodejsnode.exe --inspect-brk=29182 app.js

      Debugger
      listening on ws://127.0.0.1:29182/c2a39cf7-ab13-4sd1b-afs5-eb9wqwq5de9




      I have setup a breakpoint on my app.js as well.



      I have tried to go to the



      ws://127.0.0.1:29182/c2a39cf7-ab13-4sd1b-afs5-eb9wqwq5de9


      url as shown in the debugger but it give me:




      Site cannot be reached




      error in chrome







      node.js






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 8 at 4:03









      jedujedu

      172112




      172112






















          1 Answer
          1






          active

          oldest

          votes


















          0














          No this is the port where debugger is listening you are not supposed to go to that path,you will go to your port where your nodejs server is listening and debugger will listen to that.



          For Example:
          I have a node server running on port 3000 and I have a get request like this



          app.get('/',()=>
          console.log("This is get request");
          )


          and I have a break point on this line: console.log("This is get request");. I will start server by running debugger.



          Then I will go to localhost:3000 from postman to check and debugger will called automatically.






          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%2f55056546%2fcannot-enable-debugger-for-nodejs-vscode%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














            No this is the port where debugger is listening you are not supposed to go to that path,you will go to your port where your nodejs server is listening and debugger will listen to that.



            For Example:
            I have a node server running on port 3000 and I have a get request like this



            app.get('/',()=>
            console.log("This is get request");
            )


            and I have a break point on this line: console.log("This is get request");. I will start server by running debugger.



            Then I will go to localhost:3000 from postman to check and debugger will called automatically.






            share|improve this answer



























              0














              No this is the port where debugger is listening you are not supposed to go to that path,you will go to your port where your nodejs server is listening and debugger will listen to that.



              For Example:
              I have a node server running on port 3000 and I have a get request like this



              app.get('/',()=>
              console.log("This is get request");
              )


              and I have a break point on this line: console.log("This is get request");. I will start server by running debugger.



              Then I will go to localhost:3000 from postman to check and debugger will called automatically.






              share|improve this answer

























                0












                0








                0







                No this is the port where debugger is listening you are not supposed to go to that path,you will go to your port where your nodejs server is listening and debugger will listen to that.



                For Example:
                I have a node server running on port 3000 and I have a get request like this



                app.get('/',()=>
                console.log("This is get request");
                )


                and I have a break point on this line: console.log("This is get request");. I will start server by running debugger.



                Then I will go to localhost:3000 from postman to check and debugger will called automatically.






                share|improve this answer













                No this is the port where debugger is listening you are not supposed to go to that path,you will go to your port where your nodejs server is listening and debugger will listen to that.



                For Example:
                I have a node server running on port 3000 and I have a get request like this



                app.get('/',()=>
                console.log("This is get request");
                )


                and I have a break point on this line: console.log("This is get request");. I will start server by running debugger.



                Then I will go to localhost:3000 from postman to check and debugger will called automatically.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Mar 8 at 4:37









                Zunnurain BadarZunnurain Badar

                186114




                186114





























                    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%2f55056546%2fcannot-enable-debugger-for-nodejs-vscode%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

                    1928 у кіно

                    Захаров Федір Захарович

                    Ель Греко