Node 22: DeprecationWarning: The `punycode` module is deprecated.

[Mathias-S]

Confirm this is a Node library issue and not an underlying OpenAI API issue

• This is an issue with the Node library

Describe the bug

Importing and using openai in the current LTS version of Node (v22) will give the following warning:

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

To Reproduce

1. Use the current LTS version of Node (v22)
2. Import the openai package and use it in any way, e.g.

import openai from "openai"; 
console.log(typeof openai);

3. Run the code. Node will log the aforementioned warning.

The expected behaviour is that the openai works without warnings in the current LTS version of Node.

There is no warning in older LTS versions of Node such as Node v18 and Node v20. However, as of this week, those are now in maintenance mode.

There are previous issues (#527 #750 #780) and a PR (#402) addressing this, but they have all been closed without any resolution or any new issues tracking the progress.

The root cause is the usage of node-fetch@2.7.0.

Code snippets

No response

OS

macOS

Node version

Node v22

Library version

openai v4.68.4

[oakgary]

For anyone else stumbling upon this. The current most up to date context can be found here: #402 (comment)

-> They are working on internally resturcturing the API which would fix this issue; it's taking some time.

[Mathias-S]

Latest update: The upcoming v5 release uses native fetch instead of node-fetch, which should remove this warning.

See https://community.openai.com/t/your-feedback-requested-node-js-sdk-5-0-0-alpha/1063774

[Ferchu425]

Hello, whats the status of this v5 release? is there any planned release? Else, maybe you could merge the change in the next v4 branch.

Thank you!

PS: This seems to be the same issue as #1207

[Mathias-S]

The upcoming v5 release has now been promoted from alpha to beta status.

Else, maybe you could merge the change in the next v4 branch.

node-fetch (which causes this warning) will not be removed in the v4 branch because it's a breaking change. You will have to wait until v5 is released, or try out 5.0.0-beta.0 which was released yesterday.

[RobertCraigie]

Closing this as a dupe of #1207, v5 will be promoted to stable soon :)