[BUG] Workspace symlinks go to wrong path if directory path starts with ~

[MonochromeChameleon]

Current Behavior:

On my work computer the setup that is enforced upon me is for code to be placed inside a root-level directory called ~source-code - i.e.:

MYCOMPUTER:foo monochromechameleon$ pwd
/~source-code/projects/foo

If I create a workspace in that project, the generated symlink goes to e.g. ../~source-code/projects/foo/bar rather than simply to ../bar meaning that the dependency is not properly resolved.

I've confirmed that the symlinking works correctly when the ~ is not present, and also when it is not at the very start of the directory tree. I've not checked whether the problem arises for any other special characters.

Expected Behavior:

In the example above, I would expect the symlink to point to ../bar

Steps To Reproduce:

1. create a root-level directory that starts with ~, e.g. /~something
2. create a new npm package in that directory, using the workspaces feature
3. run npm install

Environment:

• OS: MacOS Mojave 10.14.6
• Node: 14.15.0
• npm: 7.3.0

[MonochromeChameleon]

I've tracked down the source of the problem to npm-package-arg, PR here: npm/npm-package-arg#53