node-debug | OBSOLETE - functionality now built in to node-inspector | Code Inspection library

No solution was provided, so this is the best solution to date.

On inspection the debugger does in fact start.

Running this sample code:

Answering my own question as finally reached to the solution from VS Codes very helpful and great team (https://github.com/microsoft/vscode/issues/88936)

And this is how got closer to the source of the problem - got this strange behaviour, in a React Component.js file when I type the snippet ('clmi' in this case) - before the React Component File's return() statement, I get the expected behaviour. But if I type the snippet ('clmi') inside the return() statement, I dont get anything. i.e. the snippet does not give me the code completion option inside the return () statment.

The source was that VSCode was not recognizing this file to be a "javascriptreact" language type.

Solution was as below

In a React Component's .js file, try the tokens inspector via "F1 > Inspect TM Scopes" and position the cursor at those insert position. That will tell you the detected, embedded language. Depending on your grammar it might be a different language

And bleow is what I am getting.

So as you can see, this not JavaScript nor JavaScript React but the jsx-attr language. So now I had to target that type with vscode snippet

So now, I put the whole snippet in the jsx-attr type target file ~/.config/Code/User/snippets/jsx-attr.json

And now the custom snippets worked as expected.

As mentioned in the error, that file does not exist. In the most recent version of Atom (1.38.x at the time of this writing), the file electron.asar is located at Atom.app/Contents/Resources, but not inside the Atom Helper.app.

There are several issues open on GitHub with a similar error. Looks like the package is outdated and no longer actively maintained.

First, be sure you update your npm packages in Visual Studio by performing the following steps.

1. In solution explorer, expand the npm node.
   

2. Right click and choose the appropriate option.
   a. Install Missing npm Packages
   b. Update npm Packages
   

That didn't fix the issue but it doesn't hurt. Now if you rebuild your project and debug it by pressing ctrl + F5 then it will pause on the error that is causing the Node.js server to crash.

So, The server is having trouble binding to port 1337. I'm assuming that's because it's such a low port number and we're running Visual Studio as a regular user and not as an administrator. To change the port number to a higher value you can edit the app.js file in Visual Studio.

I Changed the following line

to

Now, if you save everything, rebuild the project and debug it by clicking the debug button or pressing F5 the server will successfully start. The browser will still be directed to port 1337 instead of port 65073 though. After changing the port number in the address in the browser the page loads fine.

I'm not sure how make it open to the port we set. I'll update this post if I figure that part out.

This solution perfectly works fine for me.

Try to reinstall vscode. And select 'no and never' button when you change name file it will show the pop up look like this "Automatically update imports for moved file"

https://github.com/Microsoft/vscode/issues/53832

You are not setting this.year anywhere.

In the function isLeap(), this.year is undefined hence specs for falsy are passed.

You can console.log() inside your spec and see its value any time. It will be printed to the terminal as well as the browser instance. You may try dump() as well.

Try this:

It seems that there is already an issue open on the repo for this deprecation problem. The package needs to be updated, however it seems like there hasn't been much activity in the last few months.

"logger-nodejs" is not such npm package.

Package name may be logging-nodejs. Same with your "restify-nodejs".

You can check from here

So you can check available package for nodejs on https://npmjs.com.

Note: There may be the case that previously these package exist on npm but package owner removed.