node-inspector not working from generator-angular-fullstack app - node.js

I'm pretty new to grunt, and created a new app using generator-angular-fullstack and yeoman. I'm trying to figure out how to debug.
When I run grunt serve:debug, I get a Chrome window with http://localhost:8080/debug?port=5858
I then open my application at http://localhost:9000 in another Chrome tab.
Two issues though:
If I set a break point, the debugger never hits it
I can only set breakpoints in client side js, not server side
Thanks for any help

Related

flutter web app showing blank screen after releasing on Node JS server

I have made a Flutter Web app and it is running perfectly on Debug and Release mode. But when I deploy it to my NodeJS webserver which serves the Webpage index.html from the contents which were built by running command flutter build web, I get a blank screen (White) whenever I try to access the webpage using google chrome by typing out the URL. I have inspected the webpage too but found no errors on it.
Can anyone find any reasons for this and how to solve it?

Debugging Node.js server and React client simultaneously in WebStorm 2019.2: breakpoints don't 'break'?

I've tried following the directions here -- How do I debug server and client simultaneously in WebStorm? -- but what happens is my Node app starts, a Chrome window opens with my client -- all good so far. I had set a couple of breakpoints that should be hit as the app boots up but there is no 'break' -- the app starts and works fine, but that's it. Is there some step I'm missing? Both debugging setups seem to be running (see pic)
EDIT:
Here's what I put in my configuration:

node js process name on windows

I'm new to Node.js
I created a node js sample project on WebStorm11 using the "Node.js Express App" template.
I added an html file and just opened it on browser and it worked.
My question is how I know what process on Windows is managing the requests to my application? I want to stop it through Task Manager.
Besides, I tried to stop the process by typing ctrl+c in command line and it didn't work. Any suggestions why?
Any help will be profoundly appreciated!
Seems you didn't run your Express application, did you? Opening HTML file in browser, well, just opens it on WebStorm default built-in webserver, it doesn't start your Express server. Please see https://confluence.jetbrains.com/display/WI/Running+and+debugging+Node.js+application for instructions on running Node.js applications in WebStorm

Debugging meteor app - setup node inspector

I wanted to debug meteor code and came across couple of links:
How to debug server side code in a Meteor app
https://github.com/oortcloud/unofficial-meteor-faq#how-do-i-debug-my-meteor-app
While these two links talks about using node inspector to debug the code, it does not tells you how to run the actual application and setup the break point.
I am able to run\setup node inspector but I am not sure after that how can I launch the application and set breakpoints. Please help

How to debug Node.js based web application

I have been seeking solutions for debugging Node.js based web application from days. I had tried to debug with Eclipse + Chrome debugger plugin but failed, I posted the error in this session 'Failed to get tabs for debugging' when trying to debug NodeJs with chrome debugger for Eclipse, but could not find an answer.
However, as Node.js is so popular, I have no doubt that a lot developers have the solution for debugging Node.js server JavaScript code. I appretiate if you could share me your solution of setting up an IDE (edit and debug) for Node.js server JavaScript code, or at least how to debug it.
I would suggest using node-inspector. Here is a good tutorial for setting it up. It allows you to use a browser tab to look at your code, set breakpoints, and step through it. Additionally, you can start node with the flag --debug-brk and it will insert a break point on the first line, if you need to debug something that happens on startup.
There are several tools to debug a node application. A great ressource has been postet on Github recently.
A simple debugging setup might be just adding a breakpoint to your code and start node in debug mode like this:
Example code with use of debugger, a manual breakpoint.
app.get('/foo', function(req, res) {
var something = 123;
debugger; // execution stops if this point is reached
foo(something);
});
Start node in debug mode:
$ node debug app.js
Once you started the application in debug mode you use the application (e.g., navigate to the ressource with your browser) and once a breakpoint occurs, the execution stops and you have a debugger environment in your terminal.
Try to use Weinre (WEb INspector REmote). It's a node app help you debug UI, log for web app on devices.
It hope it can help you.

Resources