-
-
Notifications
You must be signed in to change notification settings - Fork 801
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
secure-password deps not usable #4354
Comments
This comment was marked as outdated.
This comment was marked as outdated.
thanks for you work on this @gengjiawen, this is an issue caused when next.js packs the dependencies in a way sodium-native is not able to find its pre built binary files. We had tried to handle it here blitz/packages/blitz-next/src/index-server.ts Lines 279 to 301 in 57add5f
looks like maybe the latest next.js versions has broken this fix |
The required actual dir is Maybe copied to the wrong location or lack of fallback. Also cc @timneutkens Currently you can do this to hack the runtime error cp -r ./node_modules/.pnpm/[email protected]/node_modules/sodium-native/prebuilds .next/server/app/(auth)/login |
This make production login not usable on node.js 22. |
for latest blitzjs
|
What is the problem?
not working on node.js
Paste all your error logs here:
Paste all relevant code snippets here:
What are detailed steps to reproduce this?
new blitz project
Run
blitz -v
and paste the output here:Please include below any other applicable logs and screenshots that show your problem:
Maybe remove secure-password dep, switch to argon2 or use bcrypt.
The text was updated successfully, but these errors were encountered: