Get raw user input about nopt HOT 5 CLOSED

The only way to do this is to look at the argv.original or argv.cooked, or use String as the type and perform the path resolution/checking yourself.

from nopt.

I'm putting this together for nopter and would like to support using the path module instead of strings. Is there an exposed function that can be used to parse argv.original/argv.cooked? I'd rather not have to write redundant logic.

from nopt.

I'd accept a pull req to add this data to the parsed object somehow. Maybe argv.rawFlags or something? I don't know.

from nopt.

I'll try to find some time.

from nopt.

Even using a String for a path wouldn't necessarily work coming in from the shell as it parses paths for us as well.

app path/to/file.ext

will produce:

console.log( process.argv.slice(2) );
//-> ["app","/absolute/path/to/file.ext"]

from nopt.