process.argv value is invalid

[s-a]

process.argv value is invalid

[s-a]

Sorry I am on the run...
In short: You expect the full path to a.js right?

I think this regards to this code

iron-node/app/app.js

Line 61 in 6ac6b39

result = path.resolve(process.cwd(), filename);

Will check this out soon. Maybe you can see something there?

[mik01aj]

In this case, yes. I expect exactly the same result as in Node (with or without debug, it's not very important).

In node debugger it looks tricky, because the modules get a different value than what is accessible from the debugger. What's important is the value that the modules get.

[s-a]

@mik01aj just published a new version via npm. Please let me know if this works for you.

[mik01aj]

Still the same, using [email protected]. Btw, this is what npm says; the app title bar says it's v1.2.16.

[s-a]

This indicates you are using old code.
Title bar shows package.json.version

This is what I get at:

C:\test>iron-node test.js

Can you research and give feedback what is causing this, just to be shure that this is not a general issue.

[mik01aj]

I figured it out: before I started using nvm, my npm installed packages to /usr/local/lib/node_modules and their binaries to /usr/local/bin. After I started using nvm, all packages got installed to ~/.nvm/versions/node/v0.12.7/lib/node_modules and the binaries to ~/.nvm/versions/node/v0.12.7/bin. The problem was, that /usr/local/bin was first in the $PATH variable, so I was using the package that was installed for an older version of Node.

So now I'm really using 1.5.27 and I'm happy to say that it works now! Thanks! :)

[s-a]

Ty for your feedback 👍

[mik01aj]

FYI: now I know why process.argv was different when I checked it in node debug. It was in the debugger context. To enter the script conext, I need to use the repl command.