Describe the bug

There was already an issue #1710 that was closed. Unfortunately, the same still happens, with the following call stack:

Library affected

supabase-js

Reproduction

No response

Steps to reproduce

const storageAdapter = {
  getItem: async (key: string) =>
    (await storage.getItem<string>(`local:${key}`)) || null,
  setItem: async (key: string, value: string) => {
    await storage.setItem(`local:${key}`, value);
  },
  removeItem: (key: string) => storage.removeItem(`local:${key}`),
};

supabaseClient = createClient(
  env.VITE_SUPABASE_URL,
  env.VITE_SUPABASE_ANON_KEY,
  {
    auth: {
      storage: storageAdapter,
      autoRefreshToken: true,
      persistSession: true,
      detectSessionInUrl: true,
    },
  },
);

System Info

System:
    OS: macOS 26.2
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 31.49 MB / 32.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 24.11.0
    Yarn: 1.22.11
    npm: 11.6.1
    pnpm: 10.28.2
  Browsers:
    Chrome: 144.0.7559.133
    Firefox: 147.0.3
    Safari: 26.2
  npmPackages:
    @supabase/supabase-js: ^2.95.3 => 2.95.3

Used Package Manager

pnpm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Supabase JS Library issue and not an issue with the Supabase platform. If it's a Supabase platform related bug, it should likely be reported to supabase/supabase instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.