max-mapper / max-mapper/filereader-stream
Repository not found when git ls-remote -h -t ssh://git@github.com/feross/base64-js.git
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 102
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
npm install failed when git ls-remote -h -t ssh://git@github.com/feross/base64-js.git.
$ uname
Darwin
$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.14.6
BuildVersion: 18G5033
$ git clone https://github.com/maxogden/filereader-stream
$ cd filereader-stream
$ npm install
npm WARN deprecated native-buffer-browserify@1.2.4: Use the "buffer" module (https://www.npmjs.com/package/buffer) instead
npm WARN deprecated ecstatic@1.4.1: https://github.com/jfhbrook/node-ecstatic/issues/259
npm WARN deprecated standard-format@1.6.10: standard-format is deprecated in favor of a built-in autofixer in 'standard'. Usage: standard --fix
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated core-js@1.2.7: core-js@<2.6.8 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2.
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm ERR! Error while executing:
npm ERR! /usr/local/bin/git ls-remote -h -t ssh://git@github.com/feross/base64-js.git
npm ERR!
npm ERR! ERROR: Repository not found.
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR!
npm ERR! exited with error code: 128
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/kkdd/.npm/_logs/2020-06-28T07_44_58_592Z-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 npm install in the repository and running the reported git ls-remote command for feross/base64-js. Trace where that dependency is declared and determine what change is needed for installation to complete; done means npm install succeeds without the repository-not-found error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript, nodejs
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100