Password update call does not return since v2.67.0

[felixgabler]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

When I upgrade @supabase/auth-js from v2.66.1 to v2.67.0, my password update calls to don't fire a network request and never return (using Nuxt 3 but this is called on a non-SSR page). Here is the code I use

const password = '<any_new_password>';
const { error } = await client.auth.updateUser({ password });
console.log('Complete'); // Never logs
if (isNonNullable(error)) {
    // Handle non-fatal errors directly
    switch (error.code) {
        case 'same_password':
            passwordUpdateError.value = 'errors.frontend.newPasswordShouldBeDifferent';
            return;
    }
    throw error;
}

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Install latest @supabase/supabase-js
2. Call await client.auth.updateUser({ password: 'thisIsTest4!' })

Expected behavior

Like in previous versions, the password update should work.

Screenshots

If applicable, add screenshots to help explain your problem.

System information

• OS: macOS
• Browser (if applies): Chrome
• Version of supabase-js: Works with v2.47.2 and starts failing with v2.47.6
• Version of Node.js: v22.11.0

Additional context

Add any other context about the problem here.

[j4w8n]

I just updated to supabase-js 2.47.10, and node modules shows auth-js at 2.67.3. I'm not having any issues; password updates, data and error are logging afterwards.

const { data, error } = await supabase.auth.updateUser({
  password
})
console.log(data, error)

I'm calling this code on the server-side, with SvelteKit.