Doesn't recognize shell meta-characters in file path

[ankush981]

When passing the CSV path an a string, qsv doesn't seem to recognize the tilde "~" character on Linux (Ubuntu 18.04). Here's the command history to show how to reproduce the bug:

qsv$ node bin/qsv.js -p "~/Desktop/data.csv" -h
{ [Error: ENOENT: no such file or directory, open '~/Desktop/data.csv']
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '~/Desktop/data.csv' }
(node:16684) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE]: The "chunk" argument must be one of type string or Buffer. Received type object
    at validChunk (_stream_writable.js:258:10)
    at WriteStream.Writable.write (_stream_writable.js:292:21)
    at start (/media/common/code/projects/github/qsv/bin/qsv.js:23:20)
(node:16684) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:16684) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
qsv$ node bin/qsv.js -p "/home/ankush/Desktop/data.csv" -h
QSV>

[herrfugbaum]

Thanks for the report!

Afaik node.js doesn't expand meta characters automatically see nodejs/node#684

But there is a package linked in the issue that looks promising: untildify

[ankush981]

Damn. I saw something interesting in the link you shared: nodejs/node#684 (comment). But then, who knows what other characters we might encounter later!

[herrfugbaum]

I just tested the version of #14 with ~ and $ and it seems to work

test=path/to/file.csv

node bin/qsv.js -p ~/$test

I don't know if there are more meta characters of interest.
If we find some it's probably best to open an issue/pr on the untildify repo.
What do you think?