crypto for edge runtime

[artemavrin]

No description provided.

[charmander]

globalThis.crypto is already there.

[artemavrin]

ok, I just want to fix this error in nextjs middleware

Error: The edge runtime does not support Node.js 'crypto' module.
Learn More: https://nextjs.org/docs/messages/node-module-in-edge-runtime
    at (node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/esm/server/web/globals.js:29:18)
    at (node_modules/.pnpm/[email protected]/node_modules/pg/lib/crypto/utils-webcrypto.js:21:31)
    at (webpack/bootstrap:21:0)
    at (node_modules/.pnpm/[email protected]/node_modules/pg/lib/crypto/utils.js:8:2)
    at (webpack/bootstrap:21:0)
    at (node_modules/.pnpm/[email protected]/node_modules/pg/lib/crypto/sasl.js:2:15)
    at (webpack/bootstrap:21:0)
    at (node_modules/.pnpm/[email protected]/node_modules/pg/lib/client.js:5:11)
    at (webpack/bootstrap:21:0)
    at (node_modules/.pnpm/[email protected]/node_modules/pg/lib/index.js:3:13)

how can we solve this problem?

[constantgillet]

I also have this error in NextJS middleware

[jimmy-grande]

globalThis.crypto is already there.

The problem is not that you are not using webcrypto. To make it work on edge runtime, we should get rid of the require statement.

Is it possible to change the way you select the crypto lib by saying

If the global crypto library is available, use it
otherwise use the webcrypto from the node module

which should give something like this:

const webCrypto = globalThis.crypto ?? require('node:crypto').webcrypto

What do you think @charmander ?

[charmander]

The problem is not that you are not using webcrypto.

Yes, and that’s not the problem with the pull request (which did the equivalent of globalThis.crypto || globalThis.crypto).

Your proposal looks more correct, so feel free to make a pull request.

[ETHANTALJAFFE]

Hey, still having issues with pg in my middleware.js when running nextjs locally.

Even when using [email protected] it seems like it still imports nodejs crypto like this const nodeCrypto = require('crypto').

• I am using Bun for running locally and installing packages.
• I tried uninstalling pg, deleting bun.lockb file and reinstalling and I am still seeing the nodejs crypto import inside of the utils-webcrypto file

I noticed that on github in master branch it still shows the old version https://github.com/brianc/node-postgres/blob/master/packages/pg/lib/crypto/utils-webcrypto.js

Is there a reason this was never merged? I can open a pull request with the suggested change

[artemavrin]

I figured out this issue. We should separate providers and other configuration like this

auth.config.ts

import type { NextAuthConfig } from 'next-auth';

export const authConfig = {
  pages: {
    signIn: '/login',
  },
  providers: [
    // added later in auth.ts since it requires bcrypt which is only compatible with Node.js
    // while this file is also used in non-Node.js environments
  ],
  callbacks: {
    authorized({ auth, request: { nextUrl } }) {
     // your code here ...
      return true;
    },
  },
} satisfies NextAuthConfig;

auth.ts

// imports block
export const { auth, signIn, signOut } = NextAuth({
  ...authConfig, // <- from auth.config.ts
  providers: [
    Credentials({
      async authorize(credentials) {
        // auth code here ...
      },
    }),
  ],
});

middleware.ts

import NextAuth from 'next-auth';
import { authConfig } from './auth.config';

export default NextAuth(authConfig).auth;

export const config = {
  // https://nextjs.org/docs/app/building-your-application/routing/middleware#matcher
  matcher: ['/((?!api|_next/static|_next/image|.png).*)'],
};

So you can use pg or drizzle in auth.ts and import other configs in middleware from auth.config.ts