Fails in next-auth@beta in Next.js 14 #1017

igmtink · 2023-12-16T06:47:52Z

What went wrong?
I followed this tutorial provided by Next.js 14
Using bcrypt inside of auth.config.ts of next-auth@beta in Next.js 14 causes the app to crash with unusual errors:

./node_modules/.pnpm/@[email protected]/node_modules/@mapbox/node-pre-gyp/lib/util/nw-pre-gyp/index.html
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <!doctype html>
| <html>
| <head>

Import trace for requested module:
./node_modules/.pnpm/@[email protected]/node_modules/@mapbox/node-pre-gyp/lib/util/nw-pre-gyp/index.html
./node_modules/.pnpm/@[email protected]/node_modules/@mapbox/node-pre-gyp/lib/ sync ^\.\/.*$
./node_modules/.pnpm/@[email protected]/node_modules/@mapbox/node-pre-gyp/lib/node-pre-gyp.js
./node_modules/.pnpm/[email protected]/node_modules/bcrypt/bcrypt.js
./lib/auth/auth.config.ts

What did you expect to happen?
bcrypt should work in next-auth@beta in Next.js 14
Which version of nodejs and OS?

Operating System:
  Platform: Windows 11
  Version: 23H2
Binaries:
  Node: 23.3.0
  npm: 10.2.4
  pnpm: 8.12.1
Relevant packages:
  next: 14.0.4
  next-auth: 5.0.0-beta.4
  react: ^18
  react-dom: ^18

If you find a bug, please write a failing test.
Ok, maybe once I find out more.

The text was updated successfully, but these errors were encountered:

lightify97 · 2023-12-24T08:16:58Z

@igmtink I'm experiencing the same issue. Found any solution?

userari · 2023-12-27T13:30:24Z

Experiencing same issue here :/

igmtink · 2023-12-27T13:45:38Z

i don't find any solution until now

umair-mirza · 2023-12-27T18:42:31Z

Same. Got the same error at version Next.js 13.5. No fix so far.

2wheeh · 2023-12-30T08:55:42Z

node-pre-gyp is removed in dependencies:

Remove node-pre-gyp, use prebuildify #890

but new release with this change hasn't come yet

this PR got merged last month and is bound with v6.0.0
and currently the latest version is v5.1.1

once it releases, this will be resolved (hopefully)

2wheeh · 2023-12-30T11:42:49Z

Workaround:

next-learn is taking this way.

 const authConfig = { 
  //...
  providers: [],  // Add providers with an empty array for now
 } 

 const { auth } = NextAuth({ authConfig }) // called in `middleware.ts`
 const { signIn, singOut } = NextAuth({ 
    ...authConfig,
    providers: [
    // your logic with `bcrypt`
   ],
 });

or just use bcryptjs instead.

recrsn · 2023-12-30T13:23:08Z

bcrypt will never be compatible with a server-side bundler platform.

If nextjs allows to exclude some modules to be bundled then it would work

2wheeh · 2023-12-30T13:34:54Z

bcrypt will never be compatible with a server-side bundler platform.

@recrsn would you give me a bit more explanation please?

What I understood:

next.js bundlesmiddleware.ts in edge runtime. This is separated from client bundle and server bundle.
node-pre-gyp (node-gyp-build as well) is not compatible with edge runtime.
so when the code importing node-pre-gyp is included in middleware.ts, this throws an error.

userari · 2024-01-01T09:39:04Z

I switched from bcrypt to bcryptjs and it worked for me. I had to uninstall bcrypt & @types/bcrypt and install bcryptjs & @types/bcryptjs instead and restart the app (don't know why it didn't work without an uninstallation).

Hope it will work for you

dmsoftbr · 2024-01-06T13:54:57Z

I switched from bcrypt to bcryptjs and it worked for me. I had to uninstall bcrypt & @types/bcrypt and install bcryptjs & @types/bcryptjs instead and restart the app (don't know why it didn't work without an uninstallation).

Hope it will work for you

For me, the crypto module not found error occurs using bcryptjs. Do you have this issue?

userari · 2024-01-10T19:23:18Z

I switched from bcrypt to bcryptjs and it worked for me. I had to uninstall bcrypt & @types/bcrypt and install bcryptjs & @types/bcryptjs instead and restart the app (don't know why it didn't work without an uninstallation).
Hope it will work for you

For me, the crypto module not found error occurs using bcryptjs. Do you have this issue?

I do not have this issue, try to remove node_modules, uninstall bcrypt & @types/bcrypt, and try to reinstall node_modules, hope it will work :(

nicope · 2024-01-11T08:59:26Z

same problem for me. Could make it work locally by using --force to install, but then vercel would crash when building throwing this error:

Expand 7 Lines

08:48:00.993 | Installing dependencies...
08:48:03.565 | npm ERR! code ERESOLVE
08:48:03.568 | npm ERR! ERESOLVE could not resolve
08:48:03.569 | npm ERR!
08:48:03.569 | npm ERR! While resolving: [email protected]
08:48:03.569 | npm ERR! Found: [email protected]
08:48:03.570 | npm ERR! node_modules/next
08:48:03.570 | npm ERR! next@"^14.0.5-canary.45" from the root project
08:48:03.570 | npm ERR!
08:48:03.570 | npm ERR! Could not resolve dependency:
08:48:03.570 | npm ERR! peer next@"^14" from [email protected]
08:48:03.571 | npm ERR! node_modules/next-auth
08:48:03.571 | npm ERR! next-auth@"^5.0.0-beta.4" from the root project
08:48:03.571 | npm ERR!
08:48:03.571 | npm ERR! Conflicting peer dependency: [email protected]
08:48:03.572 | npm ERR! node_modules/next
08:48:03.572 | npm ERR! peer next@"^14" from [email protected]
08:48:03.572 | npm ERR! node_modules/next-auth
08:48:03.572 | npm ERR! next-auth@"^5.0.0-beta.4" from the root project
08:48:03.572 | npm ERR!
08:48:03.572 | npm ERR! Fix the upstream dependency conflict, or retry
08:48:03.573 | npm ERR! this command with --force or --legacy-peer-deps
08:48:03.573 | npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
08:48:03.573 | npm ERR!
08:48:03.573 | npm ERR!
08:48:03.573 | npm ERR! For a full report see:
08:48:03.573 | npm ERR! /vercel/.npm/_logs/2024-01-11T08_48_01_753Z-eresolve-report.txt
08:48:03.573 |
08:48:03.573 | npm ERR! A complete log of this run can be found in: /vercel/.npm/_logs/2024-01-11T08_48_01_753Z-debug-0.log
08:48:03.588 | Error: Command "npm install" exited with 1
08:48:04.713

recrsn · 2024-01-11T11:22:29Z

@2wheeh The edge runtime is not NodeJS, any native modules will not work there

crypto is also a nodejs specific module so bcryptjs may not even work depending on how it performs platform detection.

jawkhan · 2024-03-13T09:58:25Z

Workaround:

next-learn is taking this way.

 const authConfig = { 
  //...
  providers: [],  // Add providers with an empty array for now
 } 

 const { auth } = NextAuth({ authConfig }) // called in `middleware.ts`
 const { signIn, singOut } = NextAuth({ 
    ...authConfig,
    providers: [
    // your logic with `bcrypt`
   ],
 });

or just use bcryptjs instead.

Changing from bcrypt to bcryptjs worked for me. Thank you!

shumakmanohar · 2024-05-17T15:28:57Z

This issue still exists , any solution ?

drilon305 · 2024-07-02T17:20:11Z

@shumakmanohar try and look if u made a mistake 'use client' -> 'use server' for me it worked this method.

agleymelo · 2024-09-12T22:42:30Z

middleware is all problem, remove it or found another solution 😀

VaultBoy9519 · 2024-09-21T22:45:53Z

Hello) Looks like a solution has been found
Check re-exports if you use them. Server components that use bcrypt and are exported to other locations MUST NOT be re-exported from the same index.ts as client components. Now I import functions directly from the export file - everything is fine, there are no errors.

agleymelo · 2024-09-21T22:49:29Z

Hello) Looks like a solution has been found Check re-exports if you use them. Server components that use bcrypt and are exported to other locations MUST NOT be re-exported from the same index.ts as client components. Now I import functions directly from the export file - everything is fine, there are no errors.

and a good solution is to use what you just showed

KrownWealth · 2024-10-21T10:16:44Z

Not re-exporting in index.ts works for me

mdmahendri · 2024-11-12T08:58:56Z

@shumakmanohar try and look if u made a mistake 'use client' -> 'use server' for me it worked this method.

very nice of you to mention this, problem solved! i forgot to declare 'use server'

sovetski · 2024-12-10T14:51:44Z

Any update please? for me using bcryptjs is not a good solution, the package did not get any update since 8 years..

EDIT: I just switched from bcrypt to crypto

pnpm remove @types/bcrypt bcrypt

sammycristian20 · 2024-12-12T01:57:10Z

I have this error NextRequest not appear what is your suggestion

This was referenced Dec 30, 2023

Remove unused getUser vercel/next-learn#533

Merged

Remove duplicative auth in middleware.ts vercel/next-learn#535

Closed

recrsn closed this as completed Jan 11, 2024

ankitmukhia mentioned this issue Aug 19, 2024

migrated to Auth.js v5 from nextAuth and Edge runtime compatibility fixes code100x/cms#916

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fails in next-auth@beta in Next.js 14 #1017

Fails in next-auth@beta in Next.js 14 #1017

igmtink commented Dec 16, 2023 •

edited

Loading

lightify97 commented Dec 24, 2023

userari commented Dec 27, 2023

igmtink commented Dec 27, 2023

umair-mirza commented Dec 27, 2023

2wheeh commented Dec 30, 2023 •

edited

Loading

2wheeh commented Dec 30, 2023 •

edited

Loading

recrsn commented Dec 30, 2023

2wheeh commented Dec 30, 2023 •

edited

Loading

userari commented Jan 1, 2024

dmsoftbr commented Jan 6, 2024

userari commented Jan 10, 2024

nicope commented Jan 11, 2024

recrsn commented Jan 11, 2024

jawkhan commented Mar 13, 2024

Workaround:

shumakmanohar commented May 17, 2024

drilon305 commented Jul 2, 2024

agleymelo commented Sep 12, 2024

VaultBoy9519 commented Sep 21, 2024

agleymelo commented Sep 21, 2024

KrownWealth commented Oct 21, 2024

mdmahendri commented Nov 12, 2024 •

edited

Loading

sovetski commented Dec 10, 2024 •

edited

Loading

sammycristian20 commented Dec 12, 2024

Fails in next-auth@beta in Next.js 14 #1017

Fails in next-auth@beta in Next.js 14 #1017

Comments

igmtink commented Dec 16, 2023 • edited Loading

lightify97 commented Dec 24, 2023

userari commented Dec 27, 2023

igmtink commented Dec 27, 2023

umair-mirza commented Dec 27, 2023

2wheeh commented Dec 30, 2023 • edited Loading

2wheeh commented Dec 30, 2023 • edited Loading

Workaround:

recrsn commented Dec 30, 2023

2wheeh commented Dec 30, 2023 • edited Loading

userari commented Jan 1, 2024

dmsoftbr commented Jan 6, 2024

userari commented Jan 10, 2024

nicope commented Jan 11, 2024

Expand 7 Lines

recrsn commented Jan 11, 2024

jawkhan commented Mar 13, 2024

Workaround:

shumakmanohar commented May 17, 2024

drilon305 commented Jul 2, 2024

agleymelo commented Sep 12, 2024

VaultBoy9519 commented Sep 21, 2024

agleymelo commented Sep 21, 2024

KrownWealth commented Oct 21, 2024

mdmahendri commented Nov 12, 2024 • edited Loading

sovetski commented Dec 10, 2024 • edited Loading

sammycristian20 commented Dec 12, 2024

igmtink commented Dec 16, 2023 •

edited

Loading

2wheeh commented Dec 30, 2023 •

edited

Loading

2wheeh commented Dec 30, 2023 •

edited

Loading

2wheeh commented Dec 30, 2023 •

edited

Loading

mdmahendri commented Nov 12, 2024 •

edited

Loading

sovetski commented Dec 10, 2024 •

edited

Loading