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.

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

Build fails when building offline #63

Closed
yoshuawuyts opened this issue Aug 28, 2014 · 6 comments
Closed

Build fails when building offline #63

yoshuawuyts opened this issue Aug 28, 2014 · 6 comments

Comments

@yoshuawuyts
Copy link
Contributor

Gives you some kind of error about the version, while what it should do is implement a check whether or not it can fetch the resource from the server.

@krisvandebroek
Copy link

I also cannot build offline. The output I get:
Running "nodewebkit:src" (nodewebkit) task
Fatal error: getaddrinfo ENOTFOUND

@krisvandebroek
Copy link

using grunt --stack, I got more output:

Running "nodewebkit:src" (nodewebkit) task
Fatal error: getaddrinfo ENOTFOUND
Error: getaddrinfo ENOTFOUND
    at errnoException (dns.js:37:11)
    at Object.onanswer [as oncomplete] (dns.js:124:16)

@krisvandebroek
Copy link

I tried using a later npm version: v0.11.14
Gave the same error, only is seemed to indicate which hostname that he is trying to resolve: dl.node-webkit.org.

@steffenmllr Do you have an idea? Is it possible to indicate to the node-webkit-builder to work offline?

@steffenmllr
Copy link
Contributor

Yes you can build offline, when you already have the version you want in your cache folder and specify the version in the config. If you don't specify the version it will try to get the lastest one

@krisvandebroek
Copy link

@steffenmllr: big smile on my face. When I added the version it worked. Thanks

For my curiosity, do you know a way how I could have gotten more debugging output or how to debug the grunt task so that I could have found the cause myself? Now I only know about the grunt --trace option, but that hardly gives any information.

@steffenmllr
Copy link
Contributor

not really, that is node way of telling you that something with your connection is wrong - that is nothing specific to grunt. You have a couple of options with grunt: http://gruntjs.com/using-the-cli

But I think a getaddrinfo error just doesn't give you more than that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants