Closed stevenvachon closed 9 years ago
I understand the convenience parsing the path would bring to the app, however, I don't think splitargs
is responsible for parsing the path. I think this should be done by:
path.normalize('test.js');
if you require
d path
.
Sure, but that requires knowledge of which argument is a file and which isn't and is inconsistent with operating systems. But yeah, it's going beyond an "argument splitter". Perhaps an "argument normalizer" could be written if necessary -- I'm not even sure if it is or not.
On OSX, the following command line:
produces the following value for
process.argv
:while splitargs produces:
Should paths be parsed?