I'm opening an old thread, but i missed out on this, so here's my two cents:
Regarding my plugins, i wouldn't use any, except the "main" node-webkit plugin, that provides window control and some other stuff. That plugin is good enough, although it could use some improvements. Others, (especially FS) are just "proof of concept", whatever that means.
That said, I think node-webkit is a totally new and different platform, and provides a set of features we wont see implemented in Construct soon, and i'm ok with that. We need C2 to be stable and as multi-platform as possible, and Ashely is doing a perfectly good job with this. I'm happy with current implementation of node-webkit in C2.
I believe, that We as a community need to implement a whole Node.js API as a set of plugins. It's a set of features that is platform specific, and i think it's not Ashley's job to implement them beacuse it is not in the "write once export everywhere" spirit.
But, if we as a community make those plugins, it will make a totally new and powerful way to make node-webkit apps, and provide a totally new way to use C2.
I started some of that job with socket.io and http plugins (Ok, socket.io isn't part of node.js api, but i like it), and UDP plugin for C2, but decided not to release them, because i don't see any real need for them and not any developer interested it collaboration on improving them, and i don't want to make new members of community using something that is half-done. Current unfinished plugins are enough.
I would spend my spare time on developing these plugins further, but i haven't seen any real need for them, except "wow, this is cool".
If anybody is interested in collaboration, please contact me or start a new thread, we've got the whole task list done, it's right here