ERR! Cloning into ...

[shanestillwell]

I get an error from napa when running npm install, but it seems to work fine.

Here are the legit bits of my package.json

{
  "version": "0.1.0",
  "main": "index.js",
  "private": "true",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "install": "napa"
  },
  "dependencies": {
    "express": "~3.2.6",
    "connect": "~2.12.0"
  },
  "devDependencies": {
  ...
    "napa": "~0.4.0"
  },
  "napa": {
    "angular": "angular/bower-angular",
    "ui-router": "angular-ui/ui-router"
  },
}

When I run npm install I get this

localhost:eqfront shane$ npm install

> eqfront@0.1.0 install /Users/shane/Sites/eqfront
> napa

info install git://github.com/angular/bower-angular into node_modules/angular
info install git://github.com/angular-ui/ui-router into node_modules/ui-router
ERR! Cloning into '/Users/shane/Sites/eqfront/node_modules/angular'...

ERR! Cloning into '/Users/shane/Sites/eqfront/node_modules/ui-router'...

But as I said, it clones those two packages just fine into node_modules

Any ideas?

[shama]

Hmm, it sounds like something in your environment. I cannot reproduce. I don't see any errors when trying your package.json (besides correcting the JSON error with the trailing comma at the end):

$ npm i

...

> @0.1.0 install /Users/Kyle/Documents/www/test
> napa

info install git://github.com/angular/bower-angular into node_modules/angular
info install git://github.com/angular-ui/ui-router into node_modules/ui-router
express@3.2.6 node_modules/express
├── methods@0.0.1
├── fresh@0.1.0
├── range-parser@0.0.4
├── cookie-signature@1.0.1
├── debug@0.7.4
├── buffer-crc32@0.2.1
├── cookie@0.1.0
├── commander@0.6.1
├── mkdirp@0.3.4
├── send@0.1.0 (mime@1.2.6)
└── connect@2.7.11 (pause@0.0.1, qs@0.6.5, bytes@0.2.0, cookie@0.0.5, send@0.1.1, formidable@1.0.14)

napa@0.4.0 node_modules/napa
├── rimraf@2.2.6
├── npmlog@0.0.4 (ansi@0.1.2)
└── download@0.1.10 (each-async@0.1.2, mkdirp@0.3.5, through2@0.4.1, request@2.31.0, decompress@0.1.6)

connect@2.12.0 node_modules/connect
├── uid2@0.0.3
├── methods@0.1.0
├── pause@0.0.1
├── cookie-signature@1.0.1
├── fresh@0.2.0
├── qs@0.6.6
├── debug@0.7.4
├── bytes@0.2.1
├── buffer-crc32@0.2.1
├── raw-body@1.1.2
├── batch@0.5.0
├── cookie@0.1.0
├── negotiator@0.3.0
├── send@0.1.4 (range-parser@0.0.4, mime@1.2.11)
└── multiparty@2.2.0 (stream-counter@0.2.0, readable-stream@1.1.11)

[shanestillwell]

The broken JSON was because I removed several parts of the package.json file when posting the issue. I’ll keep an eye out for what’s tripping that error.

Thanks for your time.

Shane A. Stillwell 218.499.9205

On Thu, Feb 27, 2014 at 1:11 PM, Kyle Robinson Young < notifications@github.com> wrote:

Hmm, it sounds like something in your environment. I cannot reproduce. I don't see any errors when trying your package.json (besides correcting the JSON error with the trailing comma at the end):

$ npm i

...

@0.1.0 install /Users/Kyle/Documents/www/test napa

info install git://github.com/angular/bower-angular into node_modules/angular info install git://github.com/angular-ui/ui-router into node_modules/ui-router express@3.2.6 node_modules/express ├── methods@0.0.1 ├── fresh@0.1.0 ├── range-parser@0.0.4 ├── cookie-signature@1.0.1 ├── debug@0.7.4 ├── buffer-crc32@0.2.1 ├── cookie@0.1.0 ├── commander@0.6.1 ├── mkdirp@0.3.4 ├── send@0.1.0 (mime@1.2.6) └── connect@2.7.11 (pause@0.0.1, qs@0.6.5, bytes@0.2.0, cookie@0.0.5, send@0.1.1, formidable@1.0.14)

napa@0.4.0 node_modules/napa ├── rimraf@2.2.6 ├── npmlog@0.0.4 (ansi@0.1.2) └── download@0.1.10 (each-async@0.1.2, mkdirp@0.3.5, through2@0.4.1, request@2.31.0, decompress@0.1.6)

connect@2.12.0 node_modules/connect ├── uid2@0.0.3 ├── methods@0.1.0 ├── pause@0.0.1 ├── cookie-signature@1.0.1 ├── fresh@0.2.0 ├── qs@0.6.6 ├── debug@0.7.4 ├── bytes@0.2.1 ├── buffer-crc32@0.2.1 ├── raw-body@1.1.2 ├── batch@0.5.0 ├── cookie@0.1.0 ├── negotiator@0.3.0 ├── send@0.1.4 (range-parser@0.0.4, mime@1.2.11) └── multiparty@2.2.0 (stream-counter@0.2.0, readable-stream@1.1.11)

— Reply to this email directly or view it on GitHubhttps://github.com/shama/napa/issues/8#issuecomment-36278893 .

[shama]

@shanestillwell ping, any idea what could be causing the error?

[shanestillwell]

Nope. I've used it in a different projects (same machine) and still get the same errors. If I find out the issue I'll report back to this ticket, but for now, let's just close it.

Thanks,

[shama]

See #10 for the identified solution for this. Fixed on 0.4.1.