--ipfs-repo doesn't recoginze ~

[vmx]

That's a fun issue. I ran npm-ipfs but wanted to keep the repo separate from the default one. I thought ~/.cache/npm-ipfs might be a good place if you're under Linux. So I ran:

npm-ipfs --ipfs-repo=~/.cache/npm-ipfs install

And guess what? The repository is created in the current directory in a directory called ~.

[achingbrain]

Weird, you'd have thought the shell would expand the path.

[vmx]

BTW: IIRC the message about where the repo is also said Spawning an in-process IPFS node using repo at ~/.cache/npm-ipfs`. Perhaps you want to normalize that to an absolute path.