The `punycode` module is deprecated
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- github-actions, node.js, typescript
Research direction
Start by reproducing the warnings with azure/bicep-deploy@v2, then inspect the action's TypeScript runtime and dependency tree to identify the source of punycode and url.parse usage. No files or tests are named; done means the action runs without these deprecation warnings and its relevant checks pass.
Written by the indexing model from the issue text.
Description
When using azure/bicep-deploy@v2:
(node:2313) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:2313) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
- Dominant language
- TypeScript
- Stars
- 66
- Forks
- 20
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 26
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the 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 Azure/bicep-deploy
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Azure/bicep-deploy#309 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/bicep-deploy#347 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Azure/bicep-deploy#328 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Azure/bicep-deploy#322 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Azure/bicep-deploy#304 ·
Maintainers usually reply within 1 day
All issues in Azure/bicep-deploy
Similar issues
-
normalizePath removes the Windows device namespace prefixPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
caprover/caprover-frontend#273 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ai-driven-dev/framework#1147 ·
Maintainers usually reply within 1 day
-
agent-ui bug p2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cybersemics/em#6232 ·
Maintainers usually reply within 1 day