Christopher Bennage - All Comments

re: Node.js on Windows (or JavaScript for the backend)

Bangon Kali — Sun, 04 Sep 2011 00:43:13 GMT

I've been playing around Node.JS for a while. And it's really a very good piece of technology. So I tried to build this simple Windows Installer package for NodeJS and some of its most common modules. You can check out my Google project page from here http://j.mp/nP3gDL.

Currently, the modules included are MySQL and Socket.IO because they're the most used for my part. However, I'm working on to add many more modules as they're tested to work perfectly with Windows. I hope someone can help me add more modules, until a package manager that is Windows Compatible arrives, but for the moment, I think this will do.

Additionally, i have pieced up this simple tutorial on how to add a simple chat system for an existing website (served by an existing web server such as Apache) by simply adding minimal code to the pages it serves and using NodeJS + SocketIO as another server to provide for asynchronous updates (e.g. chat) to the existing website.

re: Restarting Node.js When Your Source Changes

Lord Metroid — Mon, 29 Aug 2011 12:09:28 GMT

Reloading a module, is very easy. simply delete it from the cache and load it again.

var path = require.resolve("yourModule");

delete require.cache[path];

require("yourModule");

re: Restarting Node.js When Your Source Changes

Christopher Bennage — Mon, 22 Aug 2011 21:52:50 GMT

Thanks for the links to node-supervisor, I did miss that. (Still, it was a fun exercise.)

re: Node.js on Windows (or JavaScript for the backend)

Christopher Bennage — Mon, 22 Aug 2011 21:51:32 GMT

Regarding the console.log glitch, sorry about the typo.

re: Node.js on Windows (or JavaScript for the backend)

Christopher Bennage — Mon, 22 Aug 2011 21:50:53 GMT

@Pritesh I downloaded node.exe to a directory I named 'node.js'. It looks like you might not be executing it from the correct location.

re: Node.js on Windows (or JavaScript for the backend)

Christopher Bennage — Mon, 22 Aug 2011 21:47:21 GMT

@zvolkov regarding a web framework: I've been playing with Express (though not on Windows yet)

http://expressjs.com/

I like it, and I plan to post about it after more experience.

re: Node.js on Windows (or JavaScript for the backend)

Thanks! — Mon, 22 Aug 2011 02:07:58 GMT

Can i know who compiled node.js for Windows. I'd like to compile the latest version.

re: Restarting Node.js When Your Source Changes

Igor — Sun, 21 Aug 2011 13:24:44 GMT

Thank you for sharing. This was helpful.

re: Node.js on Windows (or JavaScript for the backend)

Pritesh — Wed, 17 Aug 2011 14:55:27 GMT

i get an error

PS C:\node.js> .node.exe .\server.js

The term '.node.exe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the s

pelling of the name, or if a path was included, verify that the path is correct and try again.

At line:1 char:10

+ .node.exe <<<< .\server.js

+ CategoryInfo : ObjectNotFound: (.node.exe:String) [], CommandNotFoundException

+ FullyQualifiedErrorId : CommandNotFoundException

re: Node.js on Windows (or JavaScript for the backend)

Pritesh — Wed, 17 Aug 2011 14:00:23 GMT

Thanks,

I'll try it out.

Keep adding more posts.

I know PHP well, but what can i do with this?

sessions, login??

re: Restarting Node.js When Your Source Changes

Julian Birch — Wed, 10 Aug 2011 19:54:01 GMT

If you'd like a node-only approach, take a look at Cluster.

learnboost.github.com/cluster

re: Restarting Node.js When Your Source Changes

Leaf — Tue, 09 Aug 2011 13:26:42 GMT

Node also has file watching capabilities, so you could do the same in Node, like this does:

github.com/.../node-supervisor

re: Restarting Node.js When Your Source Changes

James Manning — Tue, 09 Aug 2011 12:51:34 GMT

There's potentially (even likely) other places referring to laziness as a good thing in a programmer, but the one that exists in my mental cache is the Larry Wall quote.

c2.com/.../wiki

"We will encourage you to develop the three great virtues of a programmer: laziness, impatience, and hubris."

re: Restarting Node.js When Your Source Changes

Michael Hart — Tue, 09 Aug 2011 09:07:43 GMT

Weird, there are so many solutions for this, I'm surprised you didn't find one... github.com/.../node-supervisor is one of the most common

re: Node.js on Windows (or JavaScript for the backend)

Christopher Bennage — Tue, 09 Aug 2011 04:47:33 GMT

Sweet!