Chroma npm install errors?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
I am running node v8.9.4 and npm 5.6.0
When I run the npm install for chroma I get the following error:
```
npm WARN deprecated nomnom@1.6.2: Package no longer supported. Contact support@npmjs.com for more info.
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @livepeer/sdk@0.0.0
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of '@livepeer/chroma'
npm ERR! notarget
npm ERR! A complete log of this run can be found in:
npm ERR! /home/ray/.npm/_logs/2018-02-19T23_43_22_849Z-debug.log
```
Contributor guide
No contributing guide indexed for this repository
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 by reproducing the failure with npm install using the reported Node v8.9.4 and npm 5.6.0. Inspect the package metadata for @livepeer/chroma and its @livepeer/sdk@0.0.0 dependency; done means the dependency resolves and installation completes without the ETARGET error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100