Expand ~ to the current user's home directory for cli options.

So something like eslint --config="~/.eslintrc" --ignore-dir="~/eslintignore" --rulesdir="~/.config/eslint/rules" --output="~/output" works as expected and uses files in the user’s home directory.

[michaelficarra]

@tupton I don’t know of a single GNU util (or any other program) that will expand a literal ~ for you. They all let you work with a directory named ~. Expanding it would be a surprising feature.

$ mkdir "~"
$ touch "~/file"
$ cd "~/.."
$ rm "~/file"
$ rmdir "~"

[tupton]

Fair enough. I think it can be expected that users who have paths beginning with “~” have to perform this expansion before giving the directory to eslint, whether by their shell or otherwise. Thanks for taking the time to look at this.