2.49.9 breaks application code on Vercel (error 500)

Question

2.49.9 breaks application code on Vercel (error 500)

Closed this issue 3 months ago · 66 comments

Bug report

Describe the bug

    at (../../../../../node_modules/.pnpm/ws@8.18.2/node_modules/ws/browser.js:4:8)
    at (../../../../../node_modules/.pnpm/@supabase+realtime-js@2.11.9/node_modules/@supabase/realtime-js/src/RealtimeClient.ts:222:20)
    at (../../../../../node_modules/.pnpm/@supabase+realtime-js@2.11.9/node_modules/@supabase/realtime-js/src/RealtimeChannel.ts:218:18)

and the app errors with status 500

To Reproduce

Adding later

Expected behavior

I have updated from 2.49.8

Screenshots

If applicable, add screenshots to help explain your problem.

System information

Version of supabase-js: [e.g. 2.49.9]
Version of Node.js: [e.g. 22.X] (vercel)

Ari-S-123 commented 5 months ago

same

Answer 1 · 2025-06-03T10:38:43.000Z

Hi @wiesson thank you for reporting the issue, we're working on fix for it, would be great if you could try out the version "@supabase/supabase-js": "2.49.9-next.3" and confirm if that fixed it for you.

Thanks.

Answer 2 · 2025-06-03T13:28:52.000Z

I just deployed a version with "@supabase/supabase-js": "2.49.9-next.3", but I have the same error.

Error: ws does not work in the browser. Browser clients must use the native WebSocket object
    at (../../../../../node_modules/.pnpm/ws@8.18.2/node_modules/ws/browser.js:4:8)
    at (../../../../../node_modules/.pnpm/@supabase+realtime-js@2.11.10-next.1/node_modules/@supabase/realtime-js/src/RealtimeClient.ts:222:20)
    at (../../../../../node_modules/.pnpm/@supabase+realtime-js@2.11.10-next.1/node_modules/@supabase/realtime-js/src/RealtimeChannel.ts:218:18)

It works with 2.49.8, so I'm not sure if I'm supposed to change sth

Answer 3 · 2025-06-04T14:28:37.000Z

@wiesson can you check with the latest version of supabase-js?

Answer 4 · 2025-06-04T15:25:16.000Z

Hey! Seeing this error now:

../../node_modules/.pnpm/@supabase+realtime-js@2.11.10/node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
Critical dependency: the request of a dependency is an expression

Answer 5 · 2025-06-04T15:42:40.000Z

are you able to provide some example code so we can replica the issue?

also reopening this issue

Answer 6 · 2025-06-04T15:47:02.000Z

Will try to create a repro when I get back home later. Here are some additional logs & details in the meantime:

../../node_modules/.pnpm/@supabase+realtime-js@2.11.10/node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
Critical dependency: the request of a dependency is an expression

Import trace for requested module:
../../node_modules/.pnpm/@supabase+realtime-js@2.11.10/node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
../../node_modules/.pnpm/@supabase+realtime-js@2.11.10/node_modules/@supabase/realtime-js/dist/main/index.js
../../node_modules/.pnpm/@supabase+supabase-js@2.49.10/node_modules/@supabase/supabase-js/dist/module/index.js
../../node_modules/.pnpm/@supabase+ssr@0.6.1_@supabase+supabase-js@2.49.10/node_modules/@supabase/ssr/dist/module/createBrowserClient.js
../../node_modules/.pnpm/@supabase+ssr@0.6.1_@supabase+supabase-js@2.49.10/node_modules/@supabase/ssr/dist/module/index.js
./src/lib/supabase/server.ts

Actually now that I look at the import trace it looks like the ssr module is using createBrowserClient under the hood, even for the server client. Here's my supabase/server.ts (copied straight from the docs).

import 'server-only';

import { createServerClient } from '@supabase/ssr';
import type { Database } from 'common/types/database';
import { cookies } from 'next/headers';

export function createClient() {
  const cookieStore = cookies();

  return createServerClient<Database>(
    process.env.NEXT_PUBLIC_SUPABASE_URL!,
    process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!,
    {
      cookies: {
        getAll() {
          return cookieStore.getAll();
        },
        setAll(cookiesToSet) {
          try {
            cookiesToSet.forEach(({ name, value, options }) => cookieStore.set(name, value, options));
          } catch {
            // The `setAll` method was called from a Server Component.
            // This can be ignored if you have middleware refreshing
            // user sessions.
          }
        },
      },
    },
  );
}

Answer 7 · 2025-06-04T20:34:36.000Z

OK so the repro is literally the official nextjs template: npx create-next-app -e with-supabase.

#1442 might also be related.

Answer 8 · 2025-06-04T20:41:21.000Z

Error: ws does not work in the browser. Browser clients must use the native WebSocket object
    at (../../../../../node_modules/.pnpm/ws@8.18.2/node_modules/ws/browser.js:4:8)
    at (../../../../../node_modules/.pnpm/@supabase+realtime-js@2.11.10/node_modules/@supabase/realtime-js/src/RealtimeClient.ts:222:20)
    at (../../../../../node_modules/.pnpm/@supabase+realtime-js@2.11.10/node_modules/@supabase/realtime-js/src/RealtimeChannel.ts:218:18)

Still the same error, is 2.11.10 the correct version to test with?

Answer 9 · 2025-06-04T20:43:57.000Z

Yeah, it's the latest version. Honestly, I kinda expected this issue to get more attention, considering it breaks builds...

Edit: it actually doesn't break builds, it compiles with warnings

Answer 10 · 2025-06-04T21:16:38.000Z

Edit: it actually doesn't break builds, it compiles with warnings

So true! I've updated the title. I quickly created this so I wouldn't forget to do it

Answer 11 · 2025-06-05T21:06:02.000Z

@filipecabaco just wanted to ping you in case you didn't see the repro already

Answer 12 · 2025-06-06T03:56:02.000Z

  "scripts": {
    "dev": "next dev --turbopack",
    "dev:webpack": "next dev",
    "build": "next build",
    "start": "next start",
    ... other commands

  },

   "dependencies":{
     ...other libs
    "@supabase/supabase-js": "^2.49.10",
}

With Webpack

$ npm run dev:webpack

> app@0.1.0 dev:webpack
> next dev

✔ Console Ninja extension is connected to Next.js, see https://tinyurl.com/2vt8jxzw
   ▲ Next.js 15.3.3
   - Local:        http://localhost:3000
   - Network:      http://192.168.3.7:3000
   - Environments: .env.local, .env

 ✓ Starting...
 ✓ Ready in 3.7s
 ✓ Compiled /middleware in 301ms (119 modules)
 ○ Compiling /page/invoices ...
 ⚠ ./node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
Critical dependency: the request of a dependency is an expression

Import trace for requested module:
./node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
./node_modules/@supabase/realtime-js/dist/main/index.js
./node_modules/@supabase/supabase-js/dist/module/index.js
./node_modules/@supabase/ssr/dist/module/createBrowserClient.js
./node_modules/@supabase/ssr/dist/module/index.js
./src/lib/supabase/server.ts

with Turbopack

$ npm run dev

> app@0.1.0 dev
> next dev --turbopack

✔ Console Ninja extension is connected to Next.js, see https://tinyurl.com/2vt8jxzw
   ▲ Next.js 15.3.3 (Turbopack)
   - Local:        http://localhost:3000
   - Network:      http://192.168.3.7:3000
   - Environments: .env.local, .env

 ✓ Starting...
 ✓ Compiled middleware in 263ms
 ✓ Ready in 3.3s
 ○ Compiling /page/invoices ...
 ✓ Compiled /page/invoices in 8.3s
 GET /page/invoices 200 in 9892ms
 ○ Compiling /_not-found/page ...
 ✓ Compiled /_not-found/page in 1771ms
 GET /.well-known/appspecific/com.chrome.devtools.json 404 in 2375ms
 ○ Compiling /api/auth/get-session-token ...

When I run with webpack with the newest version as of today June 5, 2025, I get that error, but when I run with turbopack I don't get that error.

Then I looked in the code and noticed that it made a curious dynamic import:

            _fetch = (...args) => Promise.resolve(`${'@supabase/node-fetch'}`).then(s => __importStar(require(s))).then(({ default: fetch }) => fetch(...args));

Answer 13 · 2025-06-06T08:40:57.000Z

thank you! that's an extremely useful discovery! we might need to do the same fix we did for WS but now one for this fetch lib 😓

Answer 14 · 2025-06-06T08:56:50.000Z

next.config.ts

import type { NextConfig } from "next";

const nextConfig: NextConfig = {
  images: {
    remotePatterns: [
      {
        protocol: 'https',
        hostname: 'lh3.googleusercontent.com',
      },
    ],
  },
  webpack: (config) => {
    // Configure webpack to prefer ESM builds for browser environments
    config.resolve.mainFields = ['browser', 'module', 'main'];
    
    // Force webpack to use browser conditions for exports field resolution
    config.resolve.conditionNames = ['browser', 'module', 'import', 'default'];
    
    return config;
  },
};

export default nextConfig;

today: version 2.49.10 works with this nextconfig

i made a PR:
supabase/realtime-js#481

I ask the community for help in analyzing the fetch solution I proposed.

if you consider that new function has strong security implications in spite of being with hardcoded strings, you can ignore it, but if you consider it viable, let me know to upload a new PR

resume:

 /**
   * Use either custom fetch, if provided, or default fetch to make HTTP requests
   *
   * @internal
   */
  _resolveFetch = (customFetch?: Fetch): Fetch => {
    let _fetch: Fetch
    if (customFetch) {
      _fetch = customFetch
    } else if (typeof fetch === 'undefined') {
      _fetch = (...args) => {
        // Try dynamic import with different strategies based on environment
        return this._attemptNodeFetch(args)
      }
    } else {
      _fetch = fetch
    }
    return (...args) => _fetch(...args)
  }

  /**
   * Attempts to load node-fetch with environment-specific strategies
   * @internal
   */
  private async _attemptNodeFetch(args: Parameters<Fetch>): Promise<Response> {
    // Strategy 1: Try new Function() approach (works in most environments)
    try {
      if (this._canUseFunction()) {
        const dynamicImport = new Function(
          'specifier',
          'return import(specifier)'
        )
        const module = await dynamicImport('@supabase/node-fetch')
        return module.default(...args)
      }
    } catch (error) {
      // Continue to next strategy
    }

    // Strategy 2: Direct import (may cause webpack warnings but works in Edge environments)
    try {
      // @ts-ignore - Dynamic import fallback for Edge environments
      const module = await import('@supabase/node-fetch')
      return (module.default as Fetch)(...args)
    } catch (importError) {
      // Continue to next strategy
    }

    // Strategy 3: Fallback to require for legacy Node.js environments
    try {
      if (this._canUseFunction()) {
        const dynamicRequire = new Function(
          'specifier',
          'return require(specifier)'
        )
        const nodeFetch = dynamicRequire('@supabase/node-fetch')
        return Promise.resolve((nodeFetch.default || nodeFetch)(...args))
      } else {
        // Direct require fallback (works in some Node.js environments)
        const nodeFetch = require('@supabase/node-fetch')
        return Promise.resolve((nodeFetch.default || nodeFetch)(...args))
      }
    } catch (requireError) {
      // All strategies failed
      throw new Error(
        'fetch polyfill required: install @supabase/node-fetch or use Node.js 18+. ' +
          'Current environment does not support dynamic imports or require.'
      )
    }
  }

  /**
   * Checks if new Function() is available (CSP restrictions)
   * @internal
   */
  private _canUseFunction(): boolean {
    try {
      new Function('return true')()
      return true
    } catch {
      return false
    }
  }

Answer 15 · 2025-06-09T13:59:03.000Z

I'm having this same issue with anything above 2.49.8 using Solid-Start.

Here are my logs when upgrading to either 49.9 or 50:

node_modules/.pnpm/@supabase+supabase-js@2.50.0/node_modules/@supabase/supabase-js/dist/module/SupabaseClient.js (1:16): Error when using sourcemap for reporting an error: Can't resolve original location of error.
node_modules/.pnpm/@supabase+supabase-js@2.50.0/node_modules/@supabase/supabase-js/dist/module/SupabaseClient.js (1:24): Error when using sourcemap for reporting an error: Can't resolve original location of error.
node_modules/.pnpm/@supabase+auth-js@2.70.0/node_modules/@supabase/auth-js/dist/module/GoTrueAdminApi.js (1:13): Error when using sourcemap for reporting an error: Can't resolve original location of error.
node_modules/.pnpm/@supabase+auth-js@2.70.0/node_modules/@supabase/auth-js/dist/module/GoTrueAdminApi.js (1:21): Error when using sourcemap for reporting an error: Can't resolve original location of error.
node_modules/.pnpm/@supabase+functions-js@2.4.4/node_modules/@supabase/functions-js/dist/module/FunctionsClient.js (1:16): Error when using sourcemap for reporting an error: Can't resolve original location of error.
node_modules/.pnpm/@supabase+functions-js@2.4.4/node_modules/@supabase/functions-js/dist/module/FunctionsClient.js (1:24): Error when using sourcemap for reporting an error: Can't resolve original location of error.
node_modules/.pnpm/@supabase+supabase-js@2.50.0/node_modules/@supabase/supabase-js/dist/module/lib/fetch.js (1:16): Error when using sourcemap for reporting an error: Can't resolve original location of error.
node_modules/.pnpm/@supabase+supabase-js@2.50.0/node_modules/@supabase/supabase-js/dist/module/lib/fetch.js (1:24): Error when using sourcemap for reporting an error: Can't resolve original location of error.

2.49.8 works fine though

Answer 16 · 2025-06-11T09:44:30.000Z

I also have the Critical dependency: the request of a dependency is an expression warning since very recently.

Answer 17 · 2025-06-12T14:43:38.000Z

Adding on that we're seeing Critical dependency: the request of a dependency is an expression with 2.50.0, and that it is causing some realtime subscriptions to fail to receive any payloads.

Revert to 2.49.8 has resolved the problem

Answer 18 · 2025-06-12T16:27:32.000Z

I am also getting this same issue in 2.50.0. I have not seen any side-effects yet and it only appears as a warning.

Answer 19 · 2025-06-13T00:30:51.000Z

I am also getting these warnings after using 2.50.0. Not seeing any side effects, but it's annoying to see so many warnings each time it gets called. Please let us know once this is fixed.

Answer 20 · 2025-06-13T06:37:05.000Z

thank you! that's an extremely useful discovery! we might need to do the same fix we did for WS but now one for this fetch lib 😓

Sounds good! Let us know if there's anything we need to do/can do on our side

Answer 21 · 2025-06-13T19:32:12.000Z

Same thing for me. Thanks for your effort on this! 🙏❤️

Answer 22 · 2025-06-14T10:50:14.000Z

Facing the same issue here:

$ next dev -p 3000
▲ Next.js 15.3.3

Local: http://localhost:3000
Network: http://192.168.1.8:3000
Environments: .env.local

✓ Starting...
✓ Ready in 1292ms
✓ Compiled /middleware in 139ms (244 modules)
○ Compiling /[schema_name] ...
⚠ ./node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
Critical dependency: the request of a dependency is an expression

Import trace for requested module:
./node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
./node_modules/@supabase/realtime-js/dist/main/index.js
./node_modules/@supabase/supabase-js/dist/module/index.js
./node_modules/@supabase/ssr/dist/module/createBrowserClient.js
./node_modules/@supabase/ssr/dist/module/index.js
./utils/supabase/server.ts
./utils/auth.ts
./app/not-found.tsx
⚠ ./node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
Critical dependency: the request of a dependency is an expression

Import trace for requested module:
./node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
./node_modules/@supabase/realtime-js/dist/main/index.js
./node_modules/@supabase/supabase-js/dist/module/index.js
./node_modules/@supabase/ssr/dist/module/createBrowserClient.js
./node_modules/@supabase/ssr/dist/module/index.js
./utils/supabase/server.ts
./utils/auth.ts
./app/not-found.tsx

Answer 23 · 2025-06-16T18:22:40.000Z

i found that, your key - "anon" or "authenticated" jwt dont change permissions to read data by .select()
so you must add/create policy

Answer 24 · 2025-06-17T10:49:19.000Z

Same issue here, "@supabase/supabase-js": "^2.50.0" i get this error on project startup and realtime subscriptions are not firing at all.

../../node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
Critical dependency: the request of a dependency is an expression

Import trace for requested module:
../../node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
../../node_modules/@supabase/realtime-js/dist/main/index.js
../../node_modules/@supabase/supabase-js/dist/module/index.js
./src/lib/supabase/admin.ts
./src/app/(server)/actions/admin-actions.ts

Tried also with 2.50.1-next.5, the warning goes away but the realtime subscriptions still do not work.

Downgrading to previous versions fixes the issue

Answer 25 · 2025-06-17T11:36:06.000Z

Thanks @GBarb0 for reporting that latest next version fixed the warning.

We're working on identifying the issue with realtime subscriptions not firing.

Thanks.

Answer 26 · 2025-06-18T15:26:10.000Z

Adding my two cents: I'm trying to build and deploy a pretty straightforward Cloudflare Worker that only uses the sdk to interact with the database.

On 2.50.0 and next, the deploy fails because there's a rogue

if (typeof window === "undefined") {
  WebSocketImpl = require("ws");
} else {
  WebSocketImpl = window.WebSocket;
}

in the build, and the runtime does not like the require.

Downgrading to 2.49.8 fixes the issue.

Answer 27 · 2025-06-19T05:59:01.000Z

Same issue here, "@supabase/supabase-js": "^2.50.0" i get this error on project startup and realtime subscriptions are not firing at all.
../../node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
Critical dependency: the request of a dependency is an expression

Import trace for requested module:
../../node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
../../node_modules/@supabase/realtime-js/dist/main/index.js
../../node_modules/@supabase/supabase-js/dist/module/index.js
./src/lib/supabase/admin.ts
./src/app/(server)/actions/admin-actions.ts
Tried also with 2.50.1-next.5, the warning goes away but the realtime subscriptions still do not work.

Downgrading to previous versions fixes the issue

I have the exact same thing and need to keep it at 2.49.9 for now

Answer 28 · 2025-06-19T15:54:43.000Z

Getting the same issue on Next.JS 15.3.4 & supabase-js 2.50.0

./node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
Critical dependency: the request of a dependency is an expression

Import trace for requested module:
./node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
./node_modules/@supabase/realtime-js/dist/main/index.js
./node_modules/@supabase/supabase-js/dist/module/index.js

Answer 29 · 2025-06-19T22:11:19.000Z

Have the same problem. 🆙

Answer 30 · 2025-06-20T01:53:26.000Z

I also have had this issue for a while

Answer 31 · 2025-06-20T09:47:08.000Z

We had this issue today too

Answer 32 · 2025-06-20T18:20:56.000Z

Same issue. Crazy this has been this way for so long with no resolution in sight. Clogging up our logs.

Answer 33 · 2025-06-20T19:15:44.000Z

Hi, does anyone have a reproducible sample app I could deploy to make a few tests with latest changes? I wasn't able to reproduce it actually.

Thanks.

Answer 34 · 2025-06-20T19:17:46.000Z

Hi, does anyone have a reproducible sample app I could deploy to make a few tests with latest changes? I wasn't able to reproduce it actually.

Thanks.

@grdsdev From the comments it sounds like the Nextjs/Supabase starter template with some code to use the Supabase Broadcast will recreate the problem.

Answer 35 · 2025-06-20T19:29:47.000Z

I'm using Sveltekit with the recommendations from the supabase SSR examples (https://supabase.com/docs/guides/getting-started/tutorials/with-sveltekit?queryGroups=database-method&database-method=sql)

Answer 36 · 2025-06-20T20:18:32.000Z

Hey all, could you you please try out using v2.50.1-next.6 and let me know if that fixes your issue?

Thanks.

Answer 37 · 2025-06-21T06:13:48.000Z

We all have the same problem with Next.JS 15.3.4 & supabase-js 2.50.0

Answer 38 · 2025-06-21T22:23:37.000Z

I’m having the same issue

 "@supabase/supabase-js": "^2.50.0",
 "next": "15.3.0",

Answer 39 · 2025-06-22T06:18:41.000Z

Hey all, could you you please try out using v2.50.1-next.6 and let me know if that fixes your issue?

Thanks.

Works for me! I will do another test alter that day, but looks good so far! <3

Answer 40 · 2025-06-22T18:29:15.000Z

Hey all, could you you please try out using v2.50.1-next.6 and let me know if that fixes your issue?

Thanks.

@grdsdev I ran the following npm install @supabase/supabase-js@2.50.1-next.6 and then restarted my Nextjs server and it did NOT solve the problem:

[website]  ⚠ ../node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
[website] Critical dependency: the request of a dependency is an expression
[website] 
[website] Import trace for requested module:
[website] ../node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
[website] ../node_modules/@supabase/realtime-js/dist/main/index.js
[website] ../node_modules/@supabase/supabase-js/dist/module/index.js
[website] ../node_modules/@supabase/ssr/dist/module/createBrowserClient.js
[website] ../node_modules/@supabase/ssr/dist/module/index.js
[website] ./utils/supabase/server.ts

Did I install correctly?

Answer 41 · 2025-06-22T19:59:45.000Z

Hey all, could you you please try out using v2.50.1-next.6 and let me know if that fixes your issue?

Thanks.

I also tried updating as suggested but unfortunately the error persists

Answer 42 · 2025-06-23T20:23:31.000Z

Hey all, could you you please try out using v2.50.1-next.6 and let me know if that fixes your issue?

Thanks.

I had this error too:

../../node_modules/.pnpm/@supabase+realtime-js@2.11.10/node_modules/@supabase/realtime-js/dist/main/RealtimeClient.js
Critical dependency: the request of a dependency is an expression

v2.50.1-next.6 solved it for me. Would you release a new (intermediate) version back porting the fix?

Answer 43 · 2025-06-24T02:22:54.000Z

Hey all, could you you please try out using v2.50.1-next.6 and let me know if that fixes your issue?

Thanks.

Tried this, fixed the issue for me

Answer 44 · 2025-06-24T11:55:09.000Z

The fix just got released as v2.50.1.

Answer 45 · 2025-06-24T12:42:50.000Z

The fix just got released as v2.50.1.

Confirmed to fix the issue for me in the latest released version

Answer 46 · 2025-06-24T12:45:39.000Z

The fix just got released as v2.50.1.

Confirmed fixed for me as well (Vercel / Solid-Start)

Answer 47 · 2025-06-24T12:49:07.000Z

The fix just got released as v2.50.1.

Still having issues on Vercel with 2.50.1:

warning "@supabase/realtime-js > isows@1.0.7" has unmet peer dependency "ws@*".

> 1 | import * as WebSocket_ from "ws";
    | ^
  2 | import { getNativeWebSocket } from "./utils.js";
  3 | export const WebSocket = (() => {
  4 |     try {
https://nextjs.org/docs/messages/module-not-found
Import trace for requested module:
./node_modules/@supabase/realtime-js/dist/module/RealtimeClient.js
./node_modules/@supabase/realtime-js/dist/module/index.js
./node_modules/@supabase/supabase-js/dist/module/index.js
./src/lib/server/supabase.ts
./src/app/api/notifications/route.ts
> Build failed because of webpack errors
error Command failed with exit code 1.

Reverting to 2.49.3, works just fine. I would love to provide more information, but only the Vercel builder is having issues. It works just fine locally...

Answer 48 · 2025-08-09T07:06:41.000Z

The realtime issue seems to be back on 2.54.0? I get this error currently:

⚠ ./node_modules/.pnpm/@supabase+realtime-js@2.15.0/node_modules/@supabase/realtime-js/dist/module/lib/websocket-factory.js
Critical dependency: the request of a dependency is an expression

Import trace for requested module:
./node_modules/.pnpm/@supabase+realtime-js@2.15.0/node_modules/@supabase/realtime-js/dist/module/lib/websocket-factory.js
./node_modules/.pnpm/@supabase+realtime-js@2.15.0/node_modules/@supabase/realtime-js/dist/module/index.js
./node_modules/.pnpm/@supabase+supabase-js@2.54.0/node_modules/@supabase/supabase-js/dist/module/index.js
./src/lib/supabase/service.ts

Answer 49 · 2025-08-09T07:07:59.000Z

The realtime issue seems to be back on 2.54.0? I get this error currently:

⚠ ./node_modules/.pnpm/@supabase+realtime-js@2.15.0/node_modules/@supabase/realtime-js/dist/module/lib/websocket-factory.js
Critical dependency: the request of a dependency is an expression

Import trace for requested module:
./node_modules/.pnpm/@supabase+realtime-js@2.15.0/node_modules/@supabase/realtime-js/dist/module/lib/websocket-factory.js
./node_modules/.pnpm/@supabase+realtime-js@2.15.0/node_modules/@supabase/realtime-js/dist/module/index.js
./node_modules/.pnpm/@supabase+supabase-js@2.54.0/node_modules/@supabase/supabase-js/dist/module/index.js
./src/lib/supabase/service.ts

yes

Answer 50 · 2025-08-09T08:31:02.000Z

Same, the issue is back indeed.

Answer 51 · 2025-08-11T07:10:44.000Z

Hi all! Thank you for chiming in! It seems that my updates on realtime-js are the culprit here. I will try to fix this today! Thank you for your patience!

Answer 52 · 2025-08-11T17:28:58.000Z

@vybhavab @RoversX @unav4ila8le just to confirm. What you are seeing is a warning or an error?

Answer 53 · 2025-08-11T17:31:04.000Z

@mandarini i see it as a warning but my realtime-js websocket connection doesn't seem to be functioning or connecting to the socket due to the warning

Answer 54 · 2025-08-12T09:03:34.000Z

Re-opening until it's in a release

Answer 55 · 2025-08-12T09:25:41.000Z

Can you please test with v2.55.0?

Answer 56 · 2025-08-12T09:44:47.000Z

Thanks for the prompt fix @mandarini , unfortunately I still see the warning on v2.55.0

I am pasting my next build logs in case they can be useful:

Creating an optimized production build ...
<w> [webpack.cache.PackFileCacheStrategy] Serializing big strings (108kiB) impacts deserialization performance (consider using Buffer instead and decode when needed)
 ⚠ Compiled with warnings in 0ms

./node_modules/@supabase/realtime-js/dist/module/lib/websocket-factory.js
A Node.js API is used (process.versions at line: 34) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/@supabase/realtime-js/dist/module/lib/websocket-factory.js
./node_modules/@supabase/realtime-js/dist/module/index.js
./node_modules/@supabase/supabase-js/dist/module/index.js
./node_modules/@supabase/ssr/dist/module/createBrowserClient.js
./node_modules/@supabase/ssr/dist/module/index.js
./supabase/middleware.ts

./node_modules/@supabase/realtime-js/dist/module/lib/websocket-factory.js
A Node.js API is used (process.versions at line: 35) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/@supabase/realtime-js/dist/module/lib/websocket-factory.js
./node_modules/@supabase/realtime-js/dist/module/index.js
./node_modules/@supabase/supabase-js/dist/module/index.js
./node_modules/@supabase/ssr/dist/module/createBrowserClient.js
./node_modules/@supabase/ssr/dist/module/index.js
./supabase/middleware.ts

./node_modules/@supabase/realtime-js/dist/module/lib/websocket-factory.js
A Node.js API is used (process.versions at line: 36) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/@supabase/realtime-js/dist/module/lib/websocket-factory.js
./node_modules/@supabase/realtime-js/dist/module/index.js
./node_modules/@supabase/supabase-js/dist/module/index.js
./node_modules/@supabase/ssr/dist/module/createBrowserClient.js
./node_modules/@supabase/ssr/dist/module/index.js
./supabase/middleware.ts

./node_modules/@supabase/supabase-js/dist/module/index.js
A Node.js API is used (process.version at line: 24) which is not supported in the Edge Runtime.
Learn more: https://nextjs.org/docs/api-reference/edge-runtime

Import trace for requested module:
./node_modules/@supabase/supabase-js/dist/module/index.js
./node_modules/@supabase/ssr/dist/module/createBrowserClient.js
./node_modules/@supabase/ssr/dist/module/index.js
./supabase/middleware.ts

 ✓ Compiled successfully in 10.0s

Thanks again.

Answer 57 · 2025-08-12T09:54:23.000Z

Seems like you're using a too new Node version.

Answer 58 · 2025-08-12T09:58:04.000Z

Got it, thanks @harrybawsac
Does that mean Node 20 is the latest supported?

Answer 59 · 2025-08-12T10:55:36.000Z

No problem on @supabase/supabase-js@2.55.0, node version v24.5.0, MacOS 15.6

Thank you.

Answer 60 · 2025-08-12T10:59:37.000Z

@unav4ila8le no, we will allow you to set a transport mode. writting changelog as we speak so we can guide users properly

Answer 61 · 2025-08-12T11:31:27.000Z

@unav4ila8le can you please share a small reproduction repository? I am trying it out in my demo app (https://github.com/mandarini/my-test-sb-proj) and it seems to be working without the problematic logs, that were there before the latest update.

Answer 62 · 2025-08-13T04:46:36.000Z

@mandarini I have tested again, and the warning is not triggered on my latest build. I am not sure what changed. Thanks a lot for your support.

Answer 63 · 2025-08-13T06:36:08.000Z

@unav4ila8le wow that's so good to hear!!! Thanks for reporting back! And if it ever comes back again, do not hesitate to open a new issue and tag me! :D

Answer 64 · 2025-08-21T05:20:30.000Z

Just wanted to add an update here.

After our conversation, I noticed that the problem was still happening intermediately. I couldn't figure out why.

For anyone having the same issue on Next.js, what solved it for me once and for all was changing my runtime from edge to nodejs in my middleware. Next.js just released v15.5 where Node.js runtime support for middleware is now stable.

Hopefully this can help someone, thanks!

Answer 65 · 2025-08-21T05:23:10.000Z

FWIW, i was able to get the issue fixed by adding supabase/supabase-js to the serverExternalPackages field in my next.config.js