node-inspector: Debugger: Error: ENOENT, no such file or directory

Hi guys, I’ve trouble while debugging with node-inspector. I use Windows 7, node-inspector 0.7.4, Express: 4.8.3

I’ve this problem on two different machines.

Ok, what I could find out:

1

Error came up at this point:

fs.statSync = function(path) {
  nullCheck(path);
  return binding.stat(pathModule._makeLong(path));
};

2

The first line shows the path the debugger is looking for… The second line shows the right path Debugger - C:\Nodeapp\git bpr 23052014\bpr\node_modules\express.js Real Path - C:\Nodeapp\git bpr 23052014\bpr\node_modules\express\lib\express.js

3

He founds this pathes module.js paths: request = express

0: "c:\Nodeapp\git bpr 23052014\bpr\node_modules"
1: "c:\Nodeapp\git bpr 23052014\node_modules"
2: "c:\Nodeapp\node_modules"
3: "c:\node_modules"
4: "C:\Users\diraschk.node_modules"
5: "C:\Users\diraschk.node_libraries"
6: "c:\Program Files (x86)\lib\node"

4

and brings this path up. —> is okay! c:\Nodeapp\git bpr 23052014\bpr\node_modules\express

5

// given a path check function tryExtensions

0: ".js"
1: ".json"
2: ".node"

6

and brings this path up, but there is no file with this extension // check if the file exists and is not a directory function tryFile(requestPath) { “c:\Nodeapp\git bpr 23052014\bpr\node_modules\express.js” –> But there is not such a file! The file is here: C:\Nodeapp\git bpr 23052014\bpr\node_modules\express\lib\express.js

Is there a possibility to skip this error? Best regards, Dirk

About this issue

  • Original URL
  • State: closed
  • Created 10 years ago
  • Comments: 25 (10 by maintainers)

Most upvoted comments

Uhm, why I don’t ask screenshot at first…! It’s a normal behavior. This is not real error, but an algorithm of fs module - it try to find target file in some places, each place, where it not found, calls the exception. If you do not want to see this error, disable “Pause on uncaught errors”

If you do not want to see this error, disable “Pause on uncaught errors” --> where?

I get this same issue. It was repeatedly running in the debugger, without changing any source code or anything. I had just honed into the place the bug I was originally trying to find, and then the next time I run with the inspector it came up with this for express. I reinstalled this inspector, and recloned my node js server from github. And this time it was the same error as here except instead of express it was colors.

EDIT: Turning off break on all exceptions (pause-like button in bottom left) makes this go away. But doesn’t explain why it suddenly started nor why it suddenly was ok with express and then had a problem with colors.