Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

version 1.0.0 not available via npm? #55

Closed
dullgrin opened this issue Jan 15, 2012 · 18 comments
Closed

version 1.0.0 not available via npm? #55

dullgrin opened this issue Jan 15, 2012 · 18 comments

Comments

@dullgrin
Copy link

I'm unable to install the latest version of restify - or at least the version of code seen on github.

npm install restify

installs version 0.5.6

Attempting to

npm install restify@1.0.0

finds no such version.

Attempting to

npm install https://github.com/mcavage/node-restify.git

results in an error.

The same is true of downloading the zip from github and npm installing that.

I might be doing something wrong, but I haven't come across this before. I'd love to work with the latest version if it's available - it looks like that could be v1.0.0?
@mcavage
Copy link
Contributor

mcavage commented Jan 15, 2012

Ha :)

I've been delaying putting it in npm, mostly because I personally have not yet battle-tested it - I'm in the middle of a fairly large project, but it's not up and running/live yet. I've been doing this in my package.json:

    "dependencies": {
        "log4js": "0.4.1",
        "restify": "https://github.com/mcavage/node-restify/tarball/master"
    },

You're the second or third person that's asked though (and I haven't really told anyone about it yet) - perhaps I should just publish it but leave the npm "latest" tag pointed at the 0.5 branch.

m

@dullgrin
Copy link
Author

UPDATE: one last attempt succeeded.

sudo npm install git://github.com/mcavage/node-restify.git

succeeded. DTrace might require sudo to install?

@dullgrin
Copy link
Author

Thanks for the update - especially when you're in the midst of other work!

I think I'll go back to version 0.5.6. FWIW I get the following after successfully getting 1.0.0 to install:

robt@tell-tale:~/c-leaves/actor$ node lib/actor
[Error: Cannot find module './DTraceProviderBindings']

node.js:201
        throw e; // process.nextTick error, or 'error' event on first tick
              ^
TypeError: options.handlers must be an Array of Functions
    at /home/robt/c-leaves/actor/node_modules/restify/lib/route.js:107:15
    at Array.forEach (native)
    at new Route (/home/robt/c-leaves/actor/node_modules/restify/lib/route.js:105:22)
    at Server._addRoute (/home/robt/c-leaves/actor/node_modules/restify/lib/server.js:366:15)
    at Server.get (/home/robt/c-leaves/actor/node_modules/restify/lib/server.js:297:17)
    at Object.<anonymous> (/home/robt/c-leaves/actor/lib/actor.js:85:9)
    at Module._compile (module.js:432:26)
    at Object..js (module.js:450:10)
    at Module.load (module.js:351:31)
    at Function._load (module.js:310:12)

Thanks for all your hard work on this - restify is a great project and MUCH appreciated.

@mcavage
Copy link
Contributor

mcavage commented Jan 15, 2012

Hrm. Try doing this instead then:

git clone git://github.com/mcavage/node-restify.git
cd node-restify
npm install
npm ln

Then go to your other project, and try:

npm ln restify

If you're doing this for a new project, I'll get this out in npm, I think the 1.0 stuff is much better factoring (in particular, errors).

@dullgrin
Copy link
Author

Thanks again for the follow up. That installed v 1.0 and created the symlink. I still get the error:

[Error: Cannot find module './DTraceProviderBindings']

It looks like the dtrace-provider.js file in node-restify/node_modules/dtrace-provider dir is requiring a file that's not there?

I can work with 0.5.x no problem, but if there's anything I can do to help I'll be happy to do what I can....

@dullgrin
Copy link
Author

For what it's worth - this looks like an issue with dtrace-provider, not restify. I get the same error doing a vanilla install of just dtrace-provider. Just requiring dtrace-provider causes the error.

@mcavage
Copy link
Contributor

mcavage commented Jan 16, 2012

Hmm - what OS and what version of node/dtrace-provider? I'm using it on mac and smartos (solaris derivative), and it passes tests in travis, which is linux-based, of some kind.

@dullgrin
Copy link
Author

I'm developing on Ubuntu 11.10. I wondered if it wasn't something about my environment. I'll poke around and see what I can find. Thanks again....

@mcavage
Copy link
Contributor

mcavage commented Jan 16, 2012

Oh - are you using the node that ships with Ubuntu?

On Sun, Jan 15, 2012 at 6:22 PM, dullgrin
reply@reply.github.com
wrote:

I'm developing on Ubuntu 11.10. I wondered if it wasn't something about my environment. I'll poke around and see what I can find. Thanks again....

Reply to this email directly or view it on GitHub:
#55 (comment)

@dullgrin
Copy link
Author

I reinstalled node a month or so ago. I want to say I used apt-get but I'm not 100% sure of that. I updated since then to node v.0.6.7.

I see an entry on the dtrace-provider issues discussing ubuntu - looks like you were part of that discussion - and see that there's some issue with development headers in the node package. Although in my case, dtrace-provider installs fine - the node-waf configure and node-waf build both succeed. With one exception - during the configure the line 'checking for node path' results in not found. I don't know if that's related or not.

I may do an uninstall and reinstall of node just to see what happens. I'll take this over to the dtrace-provider issue board if that's a better place to dig deeper, but will try to keep this issue updated in case anyone else runs into the same problem.

@mcavage
Copy link
Contributor

mcavage commented Jan 16, 2012

Yeah- I was going to say this came up before - I'd try just hand-building your own node installation and see if it makes this all go away (not discouraging you from going to the dtrace board)

@mcavage
Copy link
Contributor

mcavage commented Jan 21, 2012

Hi - I published this as 1.0.0-1-rc (I'll keep it in the release candidate state for now).

@mcavage mcavage closed this as completed Jan 21, 2012
@dullgrin
Copy link
Author

Cool. Thanks, mcavage...

@mypark
Copy link

mypark commented Feb 20, 2012

I think I'm still getting this issue when I try deploying to heroku using a node 0.6.10 build pack.

[Error: Cannot find module './DTraceProviderBindings']

@panosru
Copy link

panosru commented Mar 11, 2012

I get [Error: Cannot find module './DTraceProviderBindings'] too on OSX and on CentOS and on Debian with node v0.6.12 in all these OS

@zgohr
Copy link

zgohr commented Mar 11, 2012

Same in Linux Mint 12 with node v0.6.12.

@mcavage
Copy link
Contributor

mcavage commented Mar 11, 2012

Ok - so the linux problems should be fixed by #100 (And npm 1.1.5).

With OSX - I was able to install it ok just now:

$ cd /tmp
bluesnoop:tmp mark$ npm install restify
npm http GET https://registry.npmjs.org/restify
npm http 200 https://registry.npmjs.org/restify
npm http GET https://registry.npmjs.org/async/0.1.18
npm http GET https://registry.npmjs.org/bunyan/0.6.8
npm http GET https://registry.npmjs.org/dtrace-provider/0.0.6
npm http GET https://registry.npmjs.org/lru-cache/1.0.5
npm http GET https://registry.npmjs.org/node-uuid/1.3.3
npm http GET https://registry.npmjs.org/retry/0.6.0
npm http GET https://registry.npmjs.org/formidable/1.0.9
npm http GET https://registry.npmjs.org/semver/1.0.13
npm http GET https://registry.npmjs.org/qs/0.4.2
npm http GET https://registry.npmjs.org/http-signature/0.9.8
npm http GET https://registry.npmjs.org/mime/1.2.5
npm http 304 https://registry.npmjs.org/async/0.1.18
npm http 304 https://registry.npmjs.org/lru-cache/1.0.5
npm http 304 https://registry.npmjs.org/dtrace-provider/0.0.6
npm http 304 https://registry.npmjs.org/bunyan/0.6.8
npm http 304 https://registry.npmjs.org/node-uuid/1.3.3
npm http 304 https://registry.npmjs.org/semver/1.0.13
npm http 200 https://registry.npmjs.org/retry/0.6.0
npm http GET https://registry.npmjs.org/retry/-/retry-0.6.0.tgz
npm http 304 https://registry.npmjs.org/http-signature/0.9.8
npm http 200 https://registry.npmjs.org/mime/1.2.5
npm http GET https://registry.npmjs.org/mime/-/mime-1.2.5.tgz
npm http 200 https://registry.npmjs.org/qs/0.4.2
npm http GET https://registry.npmjs.org/qs/-/qs-0.4.2.tgz
npm http 200 https://registry.npmjs.org/formidable/1.0.9
npm http GET https://registry.npmjs.org/formidable/-/formidable-1.0.9.tgz
npm http 200 https://registry.npmjs.org/retry/-/retry-0.6.0.tgz
npm http 200 https://registry.npmjs.org/mime/-/mime-1.2.5.tgz
npm http 200 https://registry.npmjs.org/qs/-/qs-0.4.2.tgz
npm http 200 https://registry.npmjs.org/formidable/-/formidable-1.0.9.tgz
npm http GET https://registry.npmjs.org/asn1/0.1.9
npm http GET https://registry.npmjs.org/sprintf/0.1.1
npm http GET https://registry.npmjs.org/ctype/0.3.1

> dtrace-provider@0.0.6 install /private/tmp/node_modules/restify/node_modules/dtrace-provider
> node-waf configure build

npm http 304 https://registry.npmjs.org/sprintf/0.1.1
npm http 304 https://registry.npmjs.org/asn1/0.1.9
npm http 304 https://registry.npmjs.org/ctype/0.3.1
Checking for program g++ or c++          : /usr/bin/g++ 
Checking for program cpp                 : /usr/bin/cpp 
Checking for program ar                  : /usr/bin/ar 
Checking for program ranlib              : /usr/bin/ranlib 
Checking for g++                         : ok  
Checking for node path                   : not found 
Checking for node prefix                 : ok /Users/mark/.nvm/v0.6.10 
'configure' finished successfully (0.387s)
Waf: Entering directory `/private/tmp/node_modules/restify/node_modules/dtrace-provider/build'
[1/4] cxx: dtrace_provider.cc -> build/Release/dtrace_provider_1.o
[2/4] cxx: dtrace_dof.cc -> build/Release/dtrace_dof_1.o
[3/4] cxx: darwin-x86_64/dtrace_probe.cc -> build/Release/darwin-x86_64/dtrace_probe_1.o
[4/4] cxx_link: build/Release/dtrace_provider_1.o build/Release/dtrace_dof_1.o build/Release/darwin-x86_64/dtrace_probe_1.o -> build/Release/DTraceProviderBindings.node
Waf: Leaving directory `/private/tmp/node_modules/restify/node_modules/dtrace-provider/build'
'build' finished successfully (1.662s)
restify@1.2.0 ./node_modules/restify 
├── lru-cache@1.0.5
├── semver@1.0.13
├── qs@0.4.2
├── retry@0.6.0
├── mime@1.2.5
├── async@0.1.18
├── node-uuid@1.3.3
├── bunyan@0.6.8
├── formidable@1.0.9
├── http-signature@0.9.8 (sprintf@0.1.1 asn1@0.1.9 ctype@0.3.1)
└── dtrace-provider@0.0.6
bluesnoop:tmp mark$ cat foo.js
 var restify = require('restify');

 restify.createServer().listen(8080);
bluesnoop:tmp mark$ node foo.js
--> OK

Can you provide more details?

@panosru
Copy link

panosru commented Apr 21, 2012

I'm still getting the same error...

root@dev:/home/panosru/domains/example.com/public_html# npm install restify
npm http GET https://registry.npmjs.org/restify
npm http 200 https://registry.npmjs.org/restify
npm http GET https://registry.npmjs.org/dtrace-provider/0.0.6
npm http GET https://registry.npmjs.org/http-signature/0.9.9
npm http GET https://registry.npmjs.org/lru-cache/1.0.5
npm http GET https://registry.npmjs.org/mime/1.2.5
npm http GET https://registry.npmjs.org/node-uuid/1.3.3
npm http GET https://registry.npmjs.org/qs/0.4.2
npm http GET https://registry.npmjs.org/retry/0.6.0
npm http GET https://registry.npmjs.org/semver/1.0.13
npm http GET https://registry.npmjs.org/bunyan/0.6.8
npm http GET https://registry.npmjs.org/byline/2.0.2
npm http 304 https://registry.npmjs.org/http-signature/0.9.9
npm http 304 https://registry.npmjs.org/node-uuid/1.3.3
npm http 304 https://registry.npmjs.org/dtrace-provider/0.0.6
npm http 304 https://registry.npmjs.org/mime/1.2.5
npm http 304 https://registry.npmjs.org/lru-cache/1.0.5
npm http 304 https://registry.npmjs.org/qs/0.4.2
npm http 304 https://registry.npmjs.org/retry/0.6.0
npm http 304 https://registry.npmjs.org/bunyan/0.6.8
npm http 304 https://registry.npmjs.org/semver/1.0.13
npm http 304 https://registry.npmjs.org/byline/2.0.2
npm http GET https://registry.npmjs.org/asn1/0.1.11
npm http GET https://registry.npmjs.org/ctype/0.5.0

> dtrace-provider@0.0.6 install /home/panosru/domains/example.com/public_html/node_modules/restify/node_modules/dtrace-provider
> node-waf configure build

Checking for program g++ or c++          : /usr/bin/g++ 
Checking for program cpp                 : /usr/bin/cpp 
Checking for program ar                  : /usr/bin/ar 
Checking for program ranlib              : /usr/bin/ranlib 
Checking for g++                         : ok  
Checking for node path                   : not found 
Checking for node prefix                 : ok /usr/local 
'configure' finished successfully (0.037s)
Waf: Entering directory `/home/panosru/domains/example.com/public_html/node_modules/restify/node_modules/dtrace-provider/build'
Waf: Leaving directory `/home/panosru/domains/example.com/public_html/node_modules/restify/node_modules/dtrace-provider/build'
'build' finished successfully (0.018s)
npm http 304 https://registry.npmjs.org/asn1/0.1.11
npm http 304 https://registry.npmjs.org/ctype/0.5.0
restify@1.4.0 ./node_modules/restify
├── lru-cache@1.0.5
├── byline@2.0.2
├── semver@1.0.13
├── retry@0.6.0
├── qs@0.4.2
├── mime@1.2.5
├── node-uuid@1.3.3
├── bunyan@0.6.8
├── dtrace-provider@0.0.6
└── http-signature@0.9.9 (asn1@0.1.11, ctype@0.5.0)

Node/NPM version:

# node -v
v0.6.15

# npm -v
1.1.18

I'm on Debian 6 64bit

# uname -a
Linux dev.panosru.com 2.6.32-5-amd64 #1 SMP Mon Jan 9 20:49:59 UTC 2012 x86_64 GNU/Linux

Thanks :)

PS I also tried to install it like you proposed

git clone git://github.com/mcavage/node-restify.git
cd node-restify
npm install
npm ln

but I got the same error, when I try to run the app...

$ NODE_ENV=development node api.js 
[Error: Cannot find module './DTraceProviderBindings']
API Server listening on port 3003

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@mcavage @panosru @mypark @zgohr @dullgrin