webpassgen VS serve

Individuals like OP, who are contemplating a switch to Bitwarden (and therefore probably do not have access to any Bitwarden clients yet) can use Bitwarden's Online Password Generator (after setting the Type option to "Passphrase"), or use other online passphrase generators (although you should probably do a little bit of due-diligence research on the generator tool that you choose before trusting it to generate the master password for your Bitwarden vault).

For your Bitwarden master password, you can use this password generator, which has 22 different English word lists (and many non-English options as well) for generating passphrases at a specified minimum entropy level. For example, select the option "Colors" in the "Alternate" box, and you will get a passphrase that looks something like this:

Yes, Bitwarden has an online passphrase generator (change the "Type" to "Passphrase"), but since you are responding to a comment by /u/atoponce, I would be remiss not to recommend Aaron's own passphrase generator tool (https://ae7.st/g/), as well as his project to audit online password/passphrase geenrators.

The only pw gen I trust (download it and run it locally): https://github.com/atoponce/webpassgen

Thanks! Note, the source code is at https://github.com/atoponce/webpassgen. I'd rather you opened it locally in your browser rather than trusting my web server. Also, it's probably high time for a new release.

I have also seen ones online like this .

I don't necessarily agree. I wrote a web-based password generator (and a command line version) that doesn't rely on any 3rd party libraries, like JQuery, Bootstrap, Vue.js, Angular, etc. with the primary focus being a clean UI and pleasant UX. I like to think I achieved those goals.

The above code starts a static server (Vercel’s serve) in port 3000. Open the URL in Chrome, open the DevTools, and click the Source tab. You’ll see main.ts as follows:

Another alternative that comes to my mind it is to use the node.js buildpack and serve the static files using serve or similar.

If you don't know how to create a backend, you can try https://npmjs.com/package/serve which is a command that will run a simple server that just serves you the files in a folder (kinda like /public does) but it runs separately from CRA/Webpack so will not affect your app. You then have to take care of fetching and updating the data with fetch() as often as you need.

In app.jsx I've tried removing all the root code and just rendered a typical "Hello World" p tag and it doesn't take nearly as long. I've also ran a basic web server infront of the build folder using serve which suggests it might webpack-dev-server that is having issues with the size of the application (Or could it be saying it's built before it actually is?).

Maybe I was lacking context a bit. I was referencing this actually: https://github.com/vercel/serve/pull/680

https://github.com/vercel/serve (nodejs implementation, therefore requires npm or yarn being installed which are package managers for node)

React.js/ Next.js / Material-UI / Browserify (bundle packaging) / Serve (static site serving) / React-Dropzone (file drag drop) / React-Idle-Timer / zxcvbn.js (Password strength estimation)

https://github.com/vercel/serve (that one should run on every system since it's implemented in NodeJS)