Warnings from npm when installing dependencies
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- node.js, typescript
- Domain
- tooling
Research direction
Start by reviewing the dependency changes from merge #57, then run npm install and npm audit to reproduce the listed warnings and vulnerabilities. Done means the deprecated-package warnings and reported vulnerabilities are addressed without introducing new installation problems.
Written by the indexing model from the issue text.
Description
After the merge of #57, there are now a few warnings when installing the dependencies which should be addressed:
npm warn deprecated [email protected]: Package no longer supported. Contact Support at
https://www.npmjs.com/support for more info.
npm warn deprecated @react-hookz/[email protected]: Package is deprecated and will be deleted
soon. Use @ver0/deep-equal instead.
npm warn deprecated [email protected]: Deprecated due to three.js version incompatibility.
Please use v0.8.0, instead.
as well as a few vulnerabilities that look like they need addressing:
added 236 packages, and audited 755 packages in 20s
178 packages are looking for funding
run `npm fund` for details
11 vulnerabilities (2 moderate, 6 high, 3 critical)
To address issues that do not require attention, run:
npm audit fix
Some issues need review, and may require choosing
a different dependency.
Run `npm audit` for details.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 15h 17m
- Merged PRs (30d)
- 50
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 DiamondLightSource/ImagingHub
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DiamondLightSource/ImagingHub#187 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
DiamondLightSource/ImagingHub#104 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
DiamondLightSource/ImagingHub#99 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DiamondLightSource/ImagingHub#89 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
DiamondLightSource/ImagingHub#44 ·
Maintainers usually reply within 1 day
All issues in DiamondLightSource/ImagingHub
Similar issues
-
awaiting-response bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
wildcard/caro#1562 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
supadata-ai/mcp#27 ·
-
content
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cosimochellini/one-piece-zero-spoiler#516 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
capricorn86/happy-dom#2485 ·
Maintainers usually reply within 2 days
-
lane: fast
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
unicef/adt-studio#946 ·
Maintainers usually reply within 2 days