!! require is not defined

[lanceflotofb]

I'm rather new to this so apologies if my question seems naive. I've downloaded the source code and am trying to run the program locally. I open the ".html" file in the "Chrome" folder using Chrome. I get the message "!! require is not defined" in the Generated password field. When I open the inspector I get the an error saying ".../Downloads/vault-master/chrome/lib/crypto-js-3.1.2.js Failed to load resource: net::ERR_FILE_NOT_FOUND".

Is there a missing file or am I not running the code properly?

[jcoglan]

When you say "downloaded the source code", what do you mean? What steps did you take to do this?

[lanceflotofb]

I downloaded the zip file, extracted the files, and then opened the vault.html file found in the /Chrome folder. I used Chrome to open vault.html

[lanceflotofb]

I was able to install the program using npm, but would still like to get the source code working. This is a great program btw!

[jcoglan]

Did you download the zip from master, or from the last stable release? The latter is here:

https://github.com/jcoglan/vault/tree/0.3.0

[lanceflotofb]

The release where I am receiving the error is 3.0. With 2.0 or 1.0, I am able to run the program through Chrome and generate passwords. However, the passwords generated with the same service name and passphrase are all different for 1.0, 2.0, and the terminal program.

[jcoglan]

The generator algorithm changed between 0.1 and 0.2 but has been stable since then. e.g. vault google -p with passphrase foo should return 8&@Wt>udB!hp[-'30YX< from 0.2 onwards.

How are you running the generator? You should be able to open web/index.html. the chrome directory is a red herring; it's the beginning of a Chrome extension that was never fully developed.

The master branch requires a build step; the original intention was for people to be able to download the source and run it as-is, but as things have developed that requirement put too much of a burden on development workflow.

[lanceflotofb]

That's what my problem was. I was running the html file inside the chrome folder rather than the web folder. Thanks for your help!