punycode deprecation warning
- Dominant language
- JavaScript
- Stars
- 17
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
When using this library on our AWS Lambda, and deployed using Helix Deploy tooling.
It generate some deprecation warning.
```
{"timestamp":"2025-06-17T08:25:43.740Z","level":"ERROR","requestId":"0e699251-9fd7-4db1-bb9c-261c4a8b2379","message":"(node:8) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.\n(Use `node --trace-deprecation ...` to show where the warning was created)"}
--
```
It seems that the issue is in tr46 dependency loaded by this module.
npm ls tr46
project
└─┬ @adobe/jwt-auth@2.0.0
└─┬ node-fetch@2.7.0
└─┬ whatwg-url@5.0.0
└── tr46@0.0.3
Are there any plans to update to a more recent version maybe of node-fetch ? which would use maybe a fix ?
example: https://github.com/jsdom/tr46/issues/63
I suppose this module should be updated as a lot of dependencies are outdated. Renovate integration would also help to keep up to date more easily.
Contributor guide
Research direction
Start by inspecting the dependency declarations and reproducing the warning from the reported node-fetch → whatwg-url → tr46 chain under Node.js. Determine which supported dependency update removes the deprecated punycode usage, then run the repository’s existing checks and confirm the warning no longer appears in the AWS Lambda scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript, nodejs
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100