No default export from supabase/node-fetch error

[richard-edwards]

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

Recently upgraded my application to the latest nuxtjs/supabase version and have been getting this error on all pages. I have looked at node-fetch source and it does look like there is a default export so not sure why this is occurring.

I have also done a full clean and reget of all dependencies.

PostgrestBuilder.ts:2 Uncaught SyntaxError: 
The requested module '/_nuxt/node_modules/.pnpm/@supabase+node-fetch@2.6.14/node_modules/@supabase/node-fetch/browser.js?v=a82b1307' 
does not provide an export named 'default' (at PostgrestBuilder.ts:2:8)

System information

• OS: linux mint
• Browser (if applies) [e.g. chrome, safari]
• Version of supabase-js: "@nuxtjs/supabase": "^1.1.3",
• Version of Node.js: 18

Additional context

[sahilpohare]

Is Someone working on this?

[mandarini]

I will be closing this issue since it has no activity for more than 2 years.

If you find that the issue persists on the latest version of our libs, feel free to open a new one, ideally with a small reproduction repository.

In any case, we'll be removing the dependency to node-fetch very soon.

Thank you for your patience and for contributing to Supabase!

[kjhughes]

I suggest leaving it open until the matter is resolved or the dependency removed, leading to resolution. There has been activity on the transitive closure of the linked issues related to this, so closing based on inactivity is, IMO, inappropriate.

[mandarini]

Thank you for voicing your very valid concern @kjhughes ! This week I am going to work on removing the node-fetch dependency from this repository, this is why I believe that closing this issue now makes sense.

Also, the code has evolved a lot since December 2023, so I would rather have the users try out the latest version and submit a new issue with that, rather than piling on an old issue.

I do hope my approach makes sense, and it does not seem very aggressive. I'm only doing this for keeping this repo clean and health. Thank you, however, in any case, for raising this.

[kjhughes]

@mandarini I'll accept a premature closing that comes with an optimistic and enthusiastic effort to resolve the issue. ;-)