matthewmueller / matthewmueller/array

npm version can't be installed.

Open
#26 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
704
Forks
53
PR merge metrics
No merged PRs in 30d

Description

Current version published at npm: 0.3.2

$ npm install array.js@0.3.2

```
npm http GET https://registry.npmjs.org/array.js/0.3.2
npm http 304 https://registry.npmjs.org/array.js/0.3.2
npm http GET https://registry.npmjs.org/emitter-component
npm http 304 https://registry.npmjs.org/emitter-component
npm ERR! Failed resolving git HEAD (git://github.com/component/to-function.git) fatal: ambiguous argument 'getter/fns': unknown revision or path not in the working tree.
npm ERR! Failed resolving git HEAD (git://github.com/component/to-function.git) Use '--' to separate paths from revisions, like this:
npm ERR! Failed resolving git HEAD (git://github.com/component/to-function.git) 'git [...] -- [...]'
npm ERR! Failed resolving git HEAD (git://github.com/component/to-function.git)
npm ERR! Error: Command failed: fatal: ambiguous argument 'getter/fns': unknown revision or path not in the working tree.
npm ERR! Use '--' to separate paths from revisions, like this:
npm ERR! 'git [...] -- [...]'
npm ERR!
npm ERR! at ChildProcess.exithandler (child_process.js:637:15)
npm ERR! at ChildProcess.EventEmitter.emit (events.js:98:17)
npm ERR! at maybeClose (child_process.js:743:16)
npm ERR! at Process.ChildProcess._handle.onexit (child_process.js:810:5)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!

npm ERR! System Darwin 13.1.0
npm ERR! command "/usr/local/Cellar/node/0.10.26/bin/node" "/usr/local/bin/npm" "install" "array.js@0.3.2"
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! code 128
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!
npm ERR! not ok code 0
```

0.2.1 works fine.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing `npm install array.js@0.3.2` with the Node.js and npm versions shown, then inspect how the published package resolves `emitter-component` and `component/to-function`. The issue is done when version 0.3.2 installs successfully, while the known 0.2.1 installation remains a useful comparison.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.