warning about imports never used

[jlemonz]

Describe the bug

"PostgrestError" is imported from external module "file://C:/smoothie-ai/lemonz-v2/node_modules/@supabase/postgrest-js/dist/index.mjs" but never used in "node_modules/@supabase/supabase-js/dist/index.mjs". since latest version

Library affected

supabase-js

Reproduction

No response

Steps to reproduce

No response

System Info

--

Used Package Manager

npm

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.

[7ttp]

Hi @jlemonz, thanks for reporting! 💚

Couldn't reproduce this on my end.
Please make sure you're on the latest version (2.89.0)
and let us know which bundler is showing this warning.

[zetttt]

I received the same warn.

`● Nuxt 4.2.2 (with Nitro 2.12.9, Vite 7.3.0 and Vue 3.5.25)
21:03:10
➜ Local: http://localhost:3000/
➜ Network: use --host to expose

ℹ Nuxt Icon client bundle consist of 63 icons with 17.57KB(uncompressed) in size 21:03:11
✔ Vite client built in 37ms 21:03:11
✔ Vite server built in 85ms 21:03:11

[21:03:12] WARN "PostgrestError" is imported from external module "file:///Users/wujun/Documents/CodeFarm/esg-next/web/node_modules/.pnpm/@supabase+postgrest-js@2.89.0/node_modules/@supabase/postgrest-js/dist/index.mjs" but never used in "node_modules/.pnpm/@supabase+supabase-js@2.89.0/node_modules/@supabase/supabase-js/dist/index.mjs".

[21:03:12] WARN "FunctionRegion", "FunctionsError", "FunctionsFetchError", "FunctionsHttpError" and "FunctionsRelayError" are imported from external module "file:///Users/wujun/Documents/CodeFarm/esg-next/web/node_modules/.pnpm/@supabase+functions-js@2.89.0/node_modules/@supabase/functions-js/dist/main/index.js" but never used in "node_modules/.pnpm/@supabase+supabase-js@2.89.0/node_modules/@supabase/supabase-js/dist/index.mjs".`

[nicokempe]

Same issue here, haven't had the time to inspect the recent commits but this right here is what I think I found out for now. I hope that I have fixed it with nicokempe@f8644cc but haven't tested it for now. PR draft: #1979

This warning is emitted by the bundler used in pnpm dev (Nuxt / Vite / Rollup pipeline in my case) during dependency optimization and tree-shaking, not at runtime.

@supabase/supabase-js imports multiple symbols from sub-packages (e.g. PostgrestError from @supabase/postgrest-js and several Functions*Error types from @supabase/functions-js) in a single import statement, while only some of those symbols are actually used at runtime(?)

The unused symbols are primarily re-exported for typing / DX purposes, but after tree-shaking removes the corresponding exports (because the consuming app doesn’t import them), the remaining import statement still includes those identifiers. This leads the bundler to report them as “imported but never used”, even though they originate from a re-export pattern inside the library.

In short:

• Runtime-used symbols (e.g. PostgrestClient, FunctionsClient) keep the import alive
• Re-export-only symbols are tree-shaken away
• The mixed import causes a false-positive unused import warning during dev builds

This is a bundling artifact of how supabase-js is built and bundled, not a user-land error.

WARN  "PostgrestError" is imported from external module "file://C:/Users/accou/WorkSpace/GitHub/DashioDevs/website/node_modules/.pnpm/@supabase+postgrest-js@2.89.0/node_modules/@supabase/postgrest-js/dist/index.mjs" but never used in "node_modules/.pnpm/@supabase+supabase-js@2.89.0/node_modules/@supabase/supabase-js/dist/index.mjs".                                                                         16:15:12
[16:15:12]  WARN  "FunctionRegion", "FunctionsError", "FunctionsFetchError", "FunctionsHttpError" and "FunctionsRelayError" are imported from external module "file://C:/Users/accou/WorkSpace/GitHub/DashioDevs/website/node_modules/.pnpm/@supabase+functions-js@2.89.0/node_modules/@supabase/functions-js/dist/main/index.js" but never used in "node_modules/.pnpm/@supabase+supabase-js@2.89.0/node_modules/@supabase/supabase-js/dist/index.mjs".

Operating system	Windows 10.0.26200
CPU	AMD Ryzen 7 5800X 8-Core Processor (16 cores)
Node.js version	v22.21.1
nuxt/cli version	3.31.3
Package manager	pnpm@10.21.0
Nuxt version	4.2.2
Nitro version	2.12.9
Builder	vite@7.3.0
Config	app, compatibilityDate, css, devServer, devtools, eslint, experimental, featureFlags, future, gtag, hooks, modules, nitro, postcss, routeRules, runtimeConfig, security, supabase, tailwindcss, turnstile, vite
Modules	@nuxt/devtools@3.1.1, @nuxt/scripts@0.11.13, @nuxt/eslint@1.12.1, @nuxt/test-utils/module@3.21.0, @nuxtjs/turnstile@1.1.1, @nuxtjs/tailwindcss@6.14.0, @nuxtjs/supabase@2.0.3, nuxt-security@2.5.0, motion-v/nuxt@1.7.4, nuxt-feature-flags-module@2025.9.1, nuxt-charts@1.0.2, nuxt-gtag@4.1.0

[onurusluca]

still getting this, why is this closed? is this even fixed?

[urbgimtam]

@onurusluca: Seems there's a relation between this and #2010 . (fix wasn't completely efficient?)

[mandarini]

It's closed as duplicate of #2010