hoodiehq / hoodie

:dog: The Offline First JavaScript Backend
Apache License 2.0
4.4k stars 461 forks source link

hoodie new ... hangs #101

Closed felixrabe closed 11 years ago

felixrabe commented 11 years ago

hoodie new hangs at Replaced package.json:

$ hoodie new hoodie-app
Creating new hoodie app 'hoodie-app' with template 'hoodiehq/my-first-hoodie'
Cloning into 'hoodie-app'...
remote: Counting objects: 812, done.
remote: Compressing objects: 100% (490/490), done.
remote: Total 812 (delta 295), reused 798 (delta 282)
Receiving objects: 100% (812/812), 1.51 MiB | 432 KiB/s, done.
Resolving deltas: 100% (295/295), done.
Replaced package.json
^C
$ hoodie -V
0.1.2

It sat there for a few minutes before I killed it.

gr2m commented 11 years ago

what does node -v & npm -v say?

janl commented 11 years ago

The next operation is npm install which obviously uses the network, maybe there is an issue with your connectivity to npm? Is this reproducible for you, e.g. does it happen when you run hoodie new again?

felixrabe commented 11 years ago
$ node -v
v0.10.12
$ npm -v
1.2.32

As a workaround, I went home, kicked the command line again, then distracted myself for a few minutes with http://browserquest.mozilla.org/. This is the result:

$ time hoodie new hoodie-app
Creating new hoodie app 'hoodie-app' with template 'hoodiehq/my-first-hoodie'
Cloning into 'hoodie-app'...
remote: Counting objects: 812, done.
remote: Compressing objects: 100% (490/490), done.
remote: Total 812 (delta 295), reused 798 (delta 282)
Receiving objects: 100% (812/812), 1.51 MiB | 620 KiB/s, done.
Resolving deltas: 100% (295/295), done.
Replaced package.json
hoodie-worker-users@0.0.6 node_modules/hoodie-worker-users
├── clone@0.1.9
├── nodemailer@0.3.44 (optimist@0.6.0, simplesmtp@0.3.4, mailcomposer@0.2.0)
└── hoodie-worker@0.0.7 (when-promisify@0.0.2, when@1.7.1, cradle@0.6.6)

hoodie-app@0.6.1 node_modules/hoodie-app
├── ports@1.1.0
├── local-tld-lib@1.0.1
├── bytes@0.2.1
├── open@0.0.3
├── async@0.2.7
├── mkdirp@0.3.5
├── semver@2.0.10
├── underscore@1.4.4
├── follow@0.9.0
├── optimist@0.5.0 (wordwrap@0.0.2)
├── multicouch@0.4.1 (which@1.0.5, ini@1.1.0, commander@1.3.0)
├── send@0.1.0 (fresh@0.1.0, range-parser@0.0.4, debug@0.7.2, mime@1.2.6)
├── cli-color@0.2.2 (memoizee@0.2.4, es5-ext@0.9.2)
├── request@2.16.6 (forever-agent@0.2.0, aws-sign@0.2.0, tunnel-agent@0.2.0, oauth-sign@0.2.0, json-stringify-safe@3.0.0, cookie-jar@0.2.0, node-uuid@1.4.0, mime@1.2.9, qs@0.5.6, hawk@0.10.2, form-data@0.0.10)
├── http-proxy@0.10.3 (colors@0.6.0-1, pkginfo@0.2.3, optimist@0.3.7, utile@0.1.7)
├── prompt@0.2.9 (revalidator@0.1.5, pkginfo@0.3.0, read@1.0.4, utile@0.1.7, winston@0.6.2)
├── corsproxy@0.2.12 (http-proxy@0.8.7)
├── couchr@0.0.13 (follow@0.8.0)
├── connect@2.7.4 (fresh@0.1.0, pause@0.0.1, cookie-signature@0.0.1, bytes@0.2.0, buffer-crc32@0.1.1, cookie@0.0.5, debug@0.7.2, formidable@1.0.11, qs@0.5.1)
├── lock@0.0.3 (tape@0.2.2)
└── hoodie-pocket@0.0.10 (hoodie-worker-shares@0.0.5, hoodie-worker-email-out@0.3.4)
Installed all dependencies
Now start our new hoodie app:

  cd hoodie-app
  hoodie start

real  1m22.285s
user  0m34.799s
sys 0m11.089s

So the issue was either connectivity at work and / or my impatience.

janl commented 11 years ago

Cool, thanks, glad it works for you!