Module not found: Can't resolve 'crypto' #7527

mwawrusch · 2023-05-11T17:30:48Z

Environment

System:
OS: macOS 13.2.1
CPU: (10) arm64 Apple M1 Pro
Memory: 1.66 GB / 32.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 18.14.2 - ~/.nvm/versions/node/v18.14.2/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v18.14.2/bin/yarn
npm: 9.5.0 - ~/.nvm/versions/node/v18.14.2/bin/npm
Browsers:
Chrome: 113.0.5672.92
Safari: 16.3

Reproduction URL

na

Describe the issue

Using the latest next-auth and next I can't create a production build. I get the following error message:

Module not found: Can't resolve 'crypto'

here:
./node_modules/next-auth/core/init.js:10:14
./node_modules/next-auth/core/lib/csrf-token.js:8:14
./node_modules/next-auth/core/lib/email/signin.js:8:14
./node_modules/next-auth/core/lib/utils.js:10:14
./node_modules/oauth/lib/oauth.js:1:12

package json:

  "dependencies": {
    "@algolia/autocomplete-js": "^1.8.3",
    "@algolia/autocomplete-theme-classic": "^1.8.3",
    "@coinbase/wallet-sdk": "3.6.3",
    "@everipedia/wagmi-magic-connector": "0.9.1",
    "@floating-ui/react": "0.22.3",
    "@fortawesome/fontawesome-svg-core": "6.4.0",
    "@fortawesome/free-brands-svg-icons": "6.4.0",
    "@fortawesome/pro-light-svg-icons": "6.4.0",
    "@fortawesome/pro-regular-svg-icons": "6.4.0",
    "@fortawesome/pro-solid-svg-icons": "6.4.0",
    "@fortawesome/pro-thin-svg-icons": "6.4.0",
    "@fortawesome/react-fontawesome": "0.2.0",
    "@headlessui/react": "1.7.13",
    "@magic-ext/connect": "6.2.0",
    "@magic-ext/oauth": "^7.1.0",
    "@magic-sdk/provider": "^13.1.0",
    "@mux/mux-video-react": "0.7.8",
    "@ramp-network/ramp-instant-sdk": "4.0.1",
    "@reservoir0x/reservoir-sdk": "0.7.3",
    "@sentry/nextjs": "7.46.0",
    "@types/node": "18.15.11",
    "@types/react": "18.0.33",
    "@types/react-dom": "18.0.11",
    "@vercel/edge-config": "0.1.5",
    "@walletconnect/sign-client": "2.3.2",
    "@walletconnect/web3-provider": "1.8.0",
    "algoliasearch": "^4.17.0",
    "blockies-react-svg": "0.0.13",
    "client-only": "^0.0.1",
    "daisyui": "2.50.0",
    "encoding": "0.1.13",
    "eth-url-parser": "1.0.2",
    "ethers": "5.7.2",
    "graphql-request": "5.1.0",
    "instantsearch.css": "^8.0.0",
    "iron-session": "6.3.1",
    "luxon": "3.3.0",
    "magic-sdk": "13.1.0",
    "next": "13.4.1",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-hook-form": "7.43.9",
    "react-hot-toast": "2.4.0",
    "react-hotkeys-hook": "4.3.8",
    "react-instantsearch-hooks-web": "6.43.0",
    "react-markdown": "8.0.7",
    "react-overlays": "5.2.1",
    "react-page-visibility": "7.0.0",
    "react-qr-code": "2.0.11",
    "rooks": "7.8.4",
    "server-only": "^0.0.1",
    "sharp": "0.32.1",
    "siwe": "2.0.5",
    "swr": "2.0.3",
    "tiny-invariant": "1.3.1",
    "typescript": "4.9.5",
    "typesense": "1.5.3",
    "typesense-instantsearch-adapter": "2.6.0",
    "usehooks-ts": "2.9.1",
    "wagmi": "0.10.15",
    "web3-token": "1.0.4",
    "web3modal": "1.9.12",
    "immer": "10.0.1",
    "next-auth": "4.22.1"
  },
  "devDependencies": {
    "@graphql-codegen/cli": "3.3.1",
    "@graphql-codegen/introspection": "3.0.1",
    "@graphql-codegen/typescript": "3.0.4",
    "@graphql-codegen/typescript-graphql-request": "4.5.9",
    "@graphql-codegen/typescript-operations": "3.0.4",
    "@graphql-codegen/typescript-react-apollo": "3.3.7",
    "@headlessui/tailwindcss": "0.1.2",
    "@tailwindcss/aspect-ratio": "0.4.2",
    "@tailwindcss/container-queries": "0.1.1",
    "@types/eth-url-parser": "^1.0.0",
    "autoprefixer": "^10.4.14",
    "eslint": "8.36.0",
    "eslint-config-next": "13.2.4",
    "lokijs": "1.5.12",
    "pino-pretty": "9.1.1",
    "postcss": "^8.4.21",
    "tailwindcss": "3.3.2"
  }

next.config.js:

**/** @type {import('next').NextConfig} */
const nextConfig = {
  experimental: {
    appDir: true,
    serverActions: true,
  },
  productionBrowserSourceMaps: false,
  basePath: '', 
  images: {
    remotePatterns: [
      {
        protocol: 'https',
        hostname: 'tokens.rojiapi.com',
        port: '',
        pathname: '/**',
      },
    ],
  },
}

module.exports = nextConfig

How to reproduce

See above

Expected behavior

It should compile.

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

balazsorban44 · 2023-05-11T22:29:00Z

Without a reproduction, it's hard to say anything. You likely just need to bump Next.js/Node.js though. We recently made sure that crypto is available in all environments where necessary:

vercel/next.js#48941

mwawrusch · 2023-05-12T03:46:09Z

Thanks. I will check it out. If not working I'll create a repo to test.

mwawrusch · 2023-05-12T04:39:18Z

Found the reason. I was using edge runtime on some routes

export const runtime = 'edge';

darcy-vitacca · 2023-05-20T02:43:21Z

Is there anyway to get this to work with edge runtime? getServerSession on an edge function is giving the above crypto error. I have the latest of all release of next-auth next etc.

willin · 2023-05-25T07:14:32Z

met the same error

willin · 2023-05-30T15:24:37Z

vercel/next.js#50444

willin · 2023-05-30T15:26:19Z

{
"dependencies": {
    "classnames": "^2.3.2",
    "dayjs": "^1.11.7",
    "dlv": "^1.1.3",
    "next": "^13.3.1",
    "next-auth": "^4.22.1",
    "punycode": "^2.3.0",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "remote-cloudflare-kv": "^0.0.1",
    "server-only": "^0.0.1",
    "swr": "^2.1.5",
    "templite": "^1.2.0",
    "theme-change": "^2.5.0"
  }
}

works on 13.3.1,

when 13.3.2 page always loading...

then 13.4 Module not found: Can't resolve 'crypto'

edwardshturman · 2023-08-01T18:14:11Z

Confirming still an issue on latest for both Next.js and NextAuth. Thanks Balázs for the clarification here; do we have an estimate for when edge function compatibility will ship? Thanks! 🙏

moorage · 2023-08-14T18:51:13Z

Ran into this issue today, running with:

    "next": "13.4.15",
    "next-auth": "^4.23.0",

UPDATE: I figured out that I had combined some code in a shared-code library that was "nodejs" runtime and "edge-only" runtime. I had to split it into two different libraries, e.g.

edge-only-lib.ts
nodejs-lib.ts

That kept the compiler from trying to combine (unused) library functions that required nodejs (e..g nextauth) into the edge endpoints.

edwardshturman · 2023-08-17T06:41:20Z

Noting that NextAuth supports the Edge Runtime in the experimental v5 and this is fixed for me; works great so far. Thanks Balázs and team :)

TimKieu · 2023-12-21T04:12:15Z

I found this on "next-auth": "^4.24.5",

10:56:20.860	▲ ./node_modules/next-auth/core/init.js:10:14
10:56:20.860	▲ Module not found: Can't resolve 'crypto'

var _crypto = require("crypto");

Can you remove or use crypto-js which supports edge runtime? Or use built-in crypto lib.

andreimacavei · 2024-03-29T13:49:53Z

I wasn't first sure why I had this problem because the error is quite misleading, as I was also using "crypto" package to generate a random string. I am using

"next": "14.2.0-canary.0",
"next-auth": "^4.24.7",

For me it's this breaks the entire edge runtime. I cannot use vercel's edge not even on a API route that has no NextAuth authentication running.

mwawrusch · 2024-03-29T13:53:38Z

I wasn't first sure why I had this problem because the error is quite misleading, as I was also using "crypto" package to generate a random string. I am using
"next": "14.2.0-canary.0",
"next-auth": "^4.24.7",
For me it's this breaks the entire edge runtime. I cannot use vercel's edge not even on a API route that has no NextAuth authentication running.

Not sure if it helps with this problem but I'd suggest to use version 5, even if it's still in beta

shuffledex · 2024-03-30T01:10:42Z

same issue here...
move to version 5 is not an easy solution, we have to adapt the code and I am not able to do right now just for test if it is work. in conclusion, using edge (next.js 14) and next-auth 4.x are incompatible right now

mwawrusch · 2024-03-30T04:41:17Z

le righ

FYI, for one app I just moved to iron-session to avoid all those headaches.

mwawrusch · 2024-03-30T04:42:04Z

same issue here... move to version 5 is not an easy solution, we have to adapt the code and I am not able to do right now just for test if it is work. in conclusion, using edge (next.js 14) and next-auth 4.x are incompatible right now

The move itself should take about 2 hours, give or take. Most time will be spent finding the correct version and docs ;)
But yeah, totally get you. I have spent way too much time on 'unproductive' tasks regarding auth lately.

ChristopherHButler · 2024-04-06T08:30:37Z

I just got everything working on v4 and then I got hit with a Serverless Function has timed out in production, uggggggh.

minodisk · 2024-04-28T14:14:19Z

I was getting this error with 4.24.7, but when I built with 5.0.0-beta.17, this error disappeared.

kristoff-cjm · 2024-05-23T18:29:14Z

I'm still getting this error using:
next-auth@5.0.0-beta.17
next@14.2.3

It seems like this issue was closed a while ago, did I miss some way to get around the error somewhere?
Are other people still getting this error?
My use case is doing next-auth in the middleware of my next app. If I import the auth function into middleware at all it won't compile.

Mnigos · 2024-06-03T16:08:49Z

I'm also getting this error

    "next": "14.2.3",
    "next-auth": "^4.24.7",

mwawrusch added the triage Unseen or unconfirmed by a maintainer yet. Provide extra information in the meantime. label May 11, 2023

balazsorban44 closed this as completed May 11, 2023

This comment has been minimized.

Sign in to view

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Module not found: Can't resolve 'crypto' #7527

Module not found: Can't resolve 'crypto' #7527

mwawrusch commented May 11, 2023

balazsorban44 commented May 11, 2023

mwawrusch commented May 12, 2023

mwawrusch commented May 12, 2023

darcy-vitacca commented May 20, 2023 •

edited

willin commented May 25, 2023

willin commented May 30, 2023

willin commented May 30, 2023

edwardshturman commented Aug 1, 2023

moorage commented Aug 14, 2023 •

edited

edwardshturman commented Aug 17, 2023

TimKieu commented Dec 21, 2023 •

edited

andreimacavei commented Mar 29, 2024 •

edited

mwawrusch commented Mar 29, 2024

shuffledex commented Mar 30, 2024

mwawrusch commented Mar 30, 2024

mwawrusch commented Mar 30, 2024 •

edited

ChristopherHButler commented Apr 6, 2024

This comment has been minimized.

minodisk commented Apr 28, 2024

kristoff-cjm commented May 23, 2024

Mnigos commented Jun 3, 2024

Module not found: Can't resolve 'crypto' #7527

Module not found: Can't resolve 'crypto' #7527

Comments

mwawrusch commented May 11, 2023

Environment

Reproduction URL

Describe the issue

How to reproduce

Expected behavior

balazsorban44 commented May 11, 2023

mwawrusch commented May 12, 2023

mwawrusch commented May 12, 2023

darcy-vitacca commented May 20, 2023 • edited

willin commented May 25, 2023

willin commented May 30, 2023

willin commented May 30, 2023

edwardshturman commented Aug 1, 2023

moorage commented Aug 14, 2023 • edited

edwardshturman commented Aug 17, 2023

TimKieu commented Dec 21, 2023 • edited

andreimacavei commented Mar 29, 2024 • edited

mwawrusch commented Mar 29, 2024

shuffledex commented Mar 30, 2024

mwawrusch commented Mar 30, 2024

mwawrusch commented Mar 30, 2024 • edited

ChristopherHButler commented Apr 6, 2024

This comment has been minimized.

minodisk commented Apr 28, 2024

kristoff-cjm commented May 23, 2024

Mnigos commented Jun 3, 2024

darcy-vitacca commented May 20, 2023 •

edited

moorage commented Aug 14, 2023 •

edited

TimKieu commented Dec 21, 2023 •

edited

andreimacavei commented Mar 29, 2024 •

edited

mwawrusch commented Mar 30, 2024 •

edited