-
-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use Argon2id from "oslo/password" inside server action - Next.js #81
Comments
Using tsup.config.ts
output
|
I am running into a similar issue with both
It seems like an issue with the rust solutions, we probably need a pure js solution (even though it's slow) in order to get around bundlers |
@isaacfink were you able to find a solution for SvelteKit? |
We really need this. Deployments on SST V3 also break. Very annoying! |
+1 Having problems during my SST V3 deployments. Vercel works, but I don't want to host there. So If there is no solution, dropping Lucia/Oslo is the only option. |
Same here. |
Current version: 14.2.4
I've set up a pretty basic username/password auth. Page renders client side form, which calls upon client action inside which server action is awaited and based on what action return value is different UI is rendered (errors, confirmation toast, loading state, etc.).
Form code:
Action code:
Essentially it throws this error when trying to hash the password via Argon2id class, or any other class provided by oslo/password (Bcrypt or Scrypt).
I have done few things to try to fix this like adding "@node-rs/argon2" as separate dependency and modifying next.config.js to look like this
but none of these solutions helped. Switching to Bcrypt as standalone dependency fixes the issue, but I would like to use Argon and would like to follow recommended Lucia setup.
Looking forward to your response and if you need anything else feel free to ask!
The text was updated successfully, but these errors were encountered: