node.bcrypt.js VS lucia

Hi, I am struggling a bit with getting bcrypt to work within nextjs and was wondering if anyone could help -- I have the same issue as listed here

bcrypt: the old standby, it looks like this has fallen out of favor for new projects.

Then, there is the bcrypt npm package which is what I assumed you were talking about. If this is what you were talking about, then I'd encourage you to take another look at the repo here, though, and let me know exactly what WebAssembly you're referring to. The C++ files and header file in the src directory are pulled into the main script in the pattern used for node add-ons.

If you look at the function source in c++ it doesn’t do anything more than hash the plaintext one, validate the salt of the provided hash, and compare the hash strings.

A good way to approach writing native addons could be: * Read this intro article https://blog.sqreen.com/building-a-native-add-on-for-node-js-in-2019/ (disclaimer, I wrote this one) * Read the source code of some simple addon examples (https://github.com/uhop/node-re2, https://github.com/kelektiv/node.bcrypt.js#readme) * read the nodejs doc on native addons * read the libuv book if you want to handle asynchronous stuff in your addons * read Node.js source code

Link: https://lucia-auth.com/

For Auch: Haven't used it myself but Lucia Auth seems to work.

If you are okay with a bit more control Lucia is a great option.

scrypt: baked into the Node crypto package; this is also a relatively common algorithm. Lucia-auth, a great new authentication library, seems to use this internally when generating passwords.

I am using Lucia Auth for authentication.

I built a starter project for developing a social media app with Sveltekit, Lucia Auth, Prisma and Faker.js. Uses sqlite for prototyping but can easily be changed to Postgres or MySQL.