Updating extensions warns: punycode module is deprecated. Please use a userland alternative instead

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

Updating extensions warns: punycode module is deprecated. Please use a userland alternative instead.

Steps to Reproduce

$ cursor --update-extensions                           
(node:60759) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `Cursor --trace-deprecation ...` to show where the warning was created)
No extension to update

Expected Behavior

Now warning

Operating System

MacOS

Version Information

3.2.11
e9ee1339915a927dfb2df4a836dd9c8337e17cc0
arm64

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. This isn’t a Cursor bug, it’s a Node.js deprecation warning DEP0040 Deprecated APIs | Node.js v25.9.0 Documentation and it’s cosmetic only.

Cursor 3.2.11 ships with Electron 39 and Node 22, where the built-in punycode module is deprecated. The warning comes from a transitive dependency of one of the bundled extensions, most likely markdown-it in markdown-language-features, which still resolves the built-in punycode via require('punycode') without the node: prefix. You can see the same warning in upstream VS Code on the same Node version.

It doesn’t affect the command. As you can see, No extension to update still works fine. We don’t want to silence it with --no-deprecation because that would hide all deprecation warnings, including useful ones. So we’ll leave it as is for now. It should go away once upstream dependencies update to the userland punycode/ package.