`punycode` deprecated warning under Node 22
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- node.js, typescript
Research direction
Start from the caprover-deploy command and run the reported npm ls punycode dependency tree under Node 22. Trace the request-promise usage and evaluate the suggested replacement, including the noted breaking changes; done means the command no longer emits the punycode deprecation warning.
Written by the indexing model from the issue text.
Description
When running caprover-deploy for example, under Node 22, you get this deprecation notice:
(node:72716) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
Dependency tree (npm ls punycode)
[email protected]
+-- [email protected]
| `-- [email protected]
| `-- [email protected]
| `-- [email protected]
+-- [email protected]
| `-- [email protected]
| `-- [email protected]
| `-- [email protected]
| `-- [email protected]
| `-- [email protected]
| `-- [email protected]
| `-- [email protected] deduped
`-- [email protected]
`-- [email protected]
`-- [email protected]
Investigation
Explanation in this section here: https://www.npmjs.com/package/punycode#installation
Fix
The prod dependency tough-cookie should be updated to v5.0.0 (however it is a sub-dep, of the dep request-promise which will never receive an update)
- https://github.com/salesforce/tough-cookie/issues/456
- https://github.com/salesforce/tough-cookie/releases/v5.0.0 (note the breaking changes)
request-promise should be upgraded to another library like node-fetch, since it has been deprecated 4 years ago.
- Dominant language
- TypeScript
- Stars
- 78
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from caprover/caprover-cli
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
caprover/caprover-cli#155 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
caprover/caprover-cli#153 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
caprover/caprover-cli#144 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
caprover/caprover-cli#143 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
caprover/caprover-cli#140 ·
All issues in caprover/caprover-cli
Similar issues
-
Add: GTrekkerOpencheck:passed streams:add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area: ui Bug Payload OSS
Difficulty 1/5 Under an hour Newbie friendliness 88/100
payloadcms/payload#19839 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
external
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ClickHouse/ClickStack#3761 ·
Maintainers usually reply within 1 day
-
fix(auth): add the email OTP verification step to Pollar loginPossibly taken @akansnoro claimed this today. OpenStellar Wave
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
safetrustcr/dApp-SafeTrust#584 · 10 comments ·
Maintainers usually reply within 1 day