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

[samj]

Operating system

macOS

Joplin version

3.0.1

Desktop version info

joplin 3.0.1 (prod, darwin)

Client ID: 3f4345a7f86b42b7a88ea3ce5a48d6b0
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

Current behaviour

% joplin version
(node:12239) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
Joplin CLI Client

Copyright © 2016-2024 Laurent Cozic
joplin 3.0.1 (prod, darwin)

Client ID: 3f4345a7f86b42b7a88ea3ce5a48d6b0
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

Expected behaviour

No deprecation warning.

Logs

No response

[lendrik-kumar]

while working i discovered a issue with react and react hooks versions, what should i do . Should i update or downgrade the react version and test it??

[samj]

I'm sorry I don't know the codebase or I'd have fixed it myself! Sent via Superhuman iOS ( ***@***.*** )

…

On Sun, Dec 8 2024 at 12:42, Sanket Mehrok < ***@***.*** > wrote: while working i discovered a issue with react and react hooks versions, what should i do . Should i update or downgrade the react version and test it?? — Reply to this email directly, view it on GitHub ( #11475 (comment) ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAFRIEXOMKNIRXGEN3PVADL2ESVJVAVCNFSM6AAAAABTGMHFIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRWGM3TEMBVHA ). You are receiving this because you authored the thread. Message ID: <laurent22/joplin/issues/11475/2526372058 @ github. com>

[lendrik-kumar]

ok no problem, I'll find some other way

[personalizedrefrigerator]

If I generate a stack trace using NODE_OPTIONS=--trace-deprecation yarn start, the warning is traced to:

• markdown-it v13.0.2. Based on the changelog for markdown-it v14, upgrading may fix the issue.
• whatwg-url v5.0.0 used by node-fetch v2.
  • node-fetch v3 seems to require ES modules.
  • For node-fetch v2, see this upstream issue.
  • Switching to the NodeJS built-in fetch might be an option, but it would need to be verified that this doesn't cause sync regressions (both on CLI and desktop).

If I:

1. Upgrade markdown-it to v14.1.0 and
2. Remove the node-fetch dependency,

then the CLI application starts without the warning.

[personalizedrefrigerator]

I'm linking to a related commit: 817f3bc. Thank you @pedr for fixing the issue!

The fix should be in v3.2.

[samj]

Thank you! Sent via Superhuman ( ***@***.*** )

…

On Thu, Dec 12, 2024 at 3:36 PM, Henry Heino < ***@***.*** > wrote: I'm linking to a related commit: 817f3bc ( 817f3bc ). Thank you @ pedr ( https://github.com/pedr ) for fixing the issue! The fix should be in v3.2. — Reply to this email directly, view it on GitHub ( #11475 (comment) ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAFRIEQFQ6OGWXXX3ORH5HT2FGNOBAVCNFSM6AAAAABTGMHFIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZZGEZDSOJWGY ). You are receiving this because you authored the thread. Message ID: <laurent22/joplin/issues/11475/2539129966 @ github. com>