DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.

[mathiasfoster]

Bug report

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

Describe the bug

When using Supabase-JS, I get an error about the punycode module being deprecated.

To Reproduce

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

1. npm install @supabase/supabase-js
2. node .
3. Error: DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
4. npm ls whatwg-url
5. Response: @supabase/supabase-js@2.38.4
   │ └─┬ @supabase/node-fetch@2.6.14
   │ └── whatwg-url@5.0.0

Expected behavior

No deprecation.

System information

• OS: WSL2 on Windows 10
• Version of supabase-js: ^2.38.4
• Version of Node.js: v21.1.0

[bhvngt]

I got similar error when I upgraded my node version to v21. This is due to older version of whatswg-url used inside @supabase/node-fetch.

One quick workaround till the team upgrades this dependency is to override the version in your package.json. Since I use pnpm as a package manager. I am using following snippet inside my package.json

	"pnpm": {
		"overrides": {
			"whatwg-url": "13.0.0"
		}
	}

[rossirpaulo]

any updates here?

[jk-sulis]

I would also appreciate an upgrade :)

[AdamBD]

Any schedule for this? Its an annoying warning in the main javascript SDK.

[m-shaka]

I guess there are two ways to fix this:

• release new @supabase/node-fetch based on node-fetch v3, which doesn't depend on whatwg-url, and use it from this library
• use native fetch instead of @supabase/node-fetch

In my opinion, the second is better since Node.js v18, the oldest maintained LTS, is supporting fetch.
However, that means the library will stop supporting dead versions of Node.js.
supabase is a business so it may be difficult to do that.

Anyway, I can contribute so please let me know, maintainers

[obra]

Hi supabase folks - Is there anything that users/customers can do to push this forward? Having a deprecation warning logged in our apps (and even in the happy path of the tutorials) because they're using supabase's first party js libraries feels a little bit like a broken window.

[expertzz]

I got similar error when I upgraded my node version to v21. This is due to older version of whatswg-url used inside @supabase/node-fetch.

One quick workaround till the team upgrades this dependency is to override the version in your package.json. Since I use pnpm as a package manager. I am using following snippet inside my package.json

	"pnpm": {
		"overrides": {
			"whatwg-url": "13.0.0"
		}
	}

A year later this is still the only fix

[kevinwright]

Why does this continue to be an issue after all this time when it's so trivially fixed by upgrading the whatwg-url dependency or just using native fetch?

[AlbinoGeek]

Would be nice if Supabase would handle this upgrade...

Unless you specifically run your project on the old ass "Maintenance" version (20) you are still plagued with this, making every build log unreadable in larger projects.

• NodeJS LTS is 22, which shows this warning.
• NodeJS Current is 23, which shows this warning.
• NodeJS 24 is coming around the corner, and FAILS BUILDING (punycode removed.)

[AlbinoGeek]

For those of us using anything other than pnpm the "solution" until Supabase gets on this is as follows:

package.json

You must place the version override in "resolutions" to enforce it is used across the project. "overrides" only works for direct dependencies, not those of your children's children.

  "resolutions": {
    "whatwg-url": "^13"
  },