data.json location

[anonymous1184]

If the bw.json file is next to bw binary it should use current directory as BITWARDENCLI_APPDATA_DIR (for shared environments/portability).

Of course this that makes much more sense on Windows. Still holds true if you need to access more than one account at the same time.

Checking if the file exists before looking for the envvar should do. Other option is to add a CLI option like bw --data bw.json.

cli/src/bw.ts

Line 77 in fe9268f

if (process.env.BITWARDENCLI_APPDATA_DIR) {

EDIT: file name. Using the same name for the configuration and the binary makes easier run file management commands (e.g. mv bw* foo/bar).

[kspearrin]

Do you know how to resolve the executable's directory name? __dirname won't resolve properly once packaged and an executable.

[anonymous1184]

To be honest haven't touched JS in at least 3 years, yet I still enjoy to read source code I use. The issue you describe seems from to be from WebPack.

The first and the last entries in the issue 5424 have working fixes. Wish I'd have the time to properly test for myself.

[kspearrin]

The issue comes from how the packaged binary handles __dirname. See https://github.com/zeit/pkg#snapshot-filesystem

[anonymous1184]

According to the docs either process.cwd() or path.dirname(process.execPath) should work. I can setup a test bench at end of the week, if I'm not too late maybe I can be of some help, of course I need to read a bit since I haven't write anything around Electron.

A lot of apps use it now (in this particular moment I'm running Authy, Bitwarden, Min Browser, Sedja, Slack, VSCode) so it won't be wasted time :)

[kspearrin]

Looks like process.execPath will work. See here:
d91a24a

It will try to load from ./bw-data/data.json

[anonymous1184]

Superb... is there any CI from where I can grab the executable for either Win or macOS?

[kspearrin]

https://ci.appveyor.com/project/bitwarden/cli/build/job/vbgwhqo719qyxtae/artifacts

[anonymous1184]

Not working on macOS or Windows, looks like you're using process.execPath and should be path.dirname(process.execPath)? Don't know for sure. The other option is simply process.cwd(). I can test Linux too after noon, right now I'm in work environments and... well, can't use the VMs for other than work-related.

[kspearrin]

Yes, you are correct. path.dirname(process.execPath)

Latest commit fixes that

[anonymous1184]

Working fine in macOS and Windows. Will test in CentOS in a few, post back IF findings. Thanks a lot for the dedication and promptness.