Route Handlers Crash with bcrypt (see: #46493) about next.js

[hero100era]

I got the same error when use bcrypt in a middleware. (Next 14.2.3)

[k9982874]

The same error occurs. To be honest solving all sorts of weird problems with the framework itself has made me exhausted before I even started actually coding work.

[k9982874]

Here is a "solution". I found that the promise function is allowed in the middleware.
Apparently, we can call an authentication endpoint via the fetch method.
This "auth" endpoint will verify the credentials with the bcrypt module.

This clumsy solution fulfills the requirement and while not breaking the beautiful vase!

[skyddyyu]

I got the same error when use bcrypt on async method.

[k9982874]

My final solution

• bcrypt cannot be run in middleware.
• Don't do authorization on the frontend.
• Create an endpoint in the backend and use bcrypt for authorization
• Call the signin method from @/auth file in the backend.
• Query user data from the database only in authorize callback. Do not use bcrypt to authenticate passwords

Basically, you need to do the authorization in your own backend, and ensure the credentials are valid before passing them to the authorize callback.