In my node site I call a restful API service I have built using a standard
http get. After a few hours of this communication successfully working I
find that the request stops being sent, it just waits and eventually times
out.
The API that is being called is still receiving requests from
there are lots of places that the installed modules could turn up. the best
might be to use npm ls (or link to npm), that will find you all the dirs,
and the have plugin authors add a field to their package.json that
indicates it is a plugin.
On Sat, Apr 21, 2012 at 4:04 PM, Mark Hahn
In addition to dealing with this directly, make sure you have an
uncaught exception handler:
process.on('uncaughtException', function (err) {
console.error(caught by event loop: , err.stack);
});
On Apr 20, 6:43 pm, steven loe steven@gmail.com wrote:
Node thinks the connection is
Hi it is perfect！ thanks
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to
Great. :)
On Sat, Apr 21, 2012 at 12:59 PM, Lucien Wang cg.w2...@gmail.com wrote:
Hi it is perfect！ thanks
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed
On Sat, Apr 21, 2012 at 06:11:08AM -0700, P. Douglas Reeder wrote:
In addition to dealing with this directly, make sure you have an
uncaught exception handler:
process.on('uncaughtException', function (err) {
console.error(caught by event loop: , err.stack);
});
Don't do that. When
Could you please run this gist https://gist.github.com/1511972 and tell
me what it gives on the beaglebone
Sorry this took so long to get back to but here it is running with out the
external power adapter. I seemed to have misplaced the adapter
in my cluttered desk.
So doing an `npm ls` from a process is the only way to go? Whatever it
takes.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To
A discovery process for modules would really be nice. Consider this a
feature request.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs
So doing an `npm ls` from a process is the only way to go? Whatever it
takes.
It looks like http://npmjs.org/doc/README.html#Using-npm-Programmatically
offers
another option.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
I am new to both ender vs. browserify. Can someone summarize their
differences, advantages, etc?
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
I would like to see a stack trace on uncaught exceptions. I thought the
node option --trace_exception did this but on a stack overflow I'm getting
only this in the exception object:
* uncaughtException
type*: string stack_overflow
message*: string Maximum call stack
Hello,
I'm learning how to write C++ modules, for Node.js. I'm sort of
brute-forcing my learning by looking at examples, referencing the
documentation for v8 and trial and error. The only two modules that I can
seem to think of, as a reference, are hiredis-node and node.bcrypt.js. Both
have
Here are the slides from my nodeconf talk last year. Not much about
building properly, but some approachable info about how a native module
works in node. Hope it helps.
http://marcorogers.com/nodeconf-2011/node_addons_presentation.html
:Marco
On Saturday, April 21, 2012 6:50:49 PM UTC-7,
14 matches
Mail list logo
