[Bug] "does not provide an export named 'parse'" with cookie@1.0.2 in Nuxt 4

[FlorianJoseph]

Describe the bug

Hello Supabase team 👋

I am using @nuxtjs/supabase@2.0.1 with Nuxt 4.2 and cookie@1.0.2.
When running the project, I get the following error:

Uncaught (in promise) SyntaxError: The requested module 'cookie' does not provide an export named 'parse'

It seems related to the CommonJS → ESM import in @supabase/ssr@0.7.0.

Is there a plan to fix this or a recommended workaround until a patch release?

Thanks a lot!

Screenshots

[nilesh-ProdE]

Some more context after exploring further -

likely cause - an ESM/CJS interop mismatch when importing cookie (named parse) during SSR with Nuxt/Vite + pnpm. At runtime the resolved module shape doesn’t expose parse as a named export.

workarounds:

1. pin cookie to a CJS version:

   cookie@0.5.0
   

   Reinstall and re-run.

2. if patching locally, switch to an interop‑safe import:

   import * as cookie from 'cookie'
   const { parse, serialize } = cookie
   // or:
   import cookiePkg from 'cookie'
   const { parse, serialize } = cookiePkg

suggestion - update @supabase/ssr to use an interop‑safe cookie import or align the SSR build so it works consistently across cookie 0.5.x/1.x and common bundlers.

[FlorianJoseph]

Aucune des 2 solutions ne résoute le problème

[Hallidayo]

Transferred from supabase repo.

[popadicbranislav]

Is this duplicate of the #62 ?

[FlorianJoseph]

Thanks @popadicbranislav for your help, i'll try to downgrade Nuxt 4.2.0 for Nuxt 4.1.3 and reply later

[FlorianJoseph]

@popadicbranislav thank you so much, my project works again if i downgrade Nuxt 4.2.0 -> 4.1.3