modules failing on master with --throw-deprecation
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 606
- Forks
- 157
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 3
Description
I created a project to track them: https://github.com/nodejs/citgm/projects/2
The reason is mainly the deprecation of the Buffer constructor.
Note: currently, npm itself fails to run with --throw-deprecation (https://github.com/nodejs/node/issues/23013).
You can work around it by replacing pseudoRandomBytes manually in lib/node_modules/npm/node_modules/unique-slug/index.js
Contributor 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.
Research direction
Start with the linked citgm project to identify the tracked module failures, then reproduce them under --throw-deprecation and inspect the reported deprecation locations. The issue specifically names lib/node_modules/npm/node_modules/unique-slug/index.js as an npm workaround; done means the tracked module failures are resolved, with npm's separate failure excluded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100