I looked at this module couple of weeks ago. If you check GitHub Network page
here https://github.com/sgentle/phantomjs-node/network
you'll see that a lot of people forked this project and add more functionality
to it.
There's also another binding to Phantom:
https://npmjs.org/package/node-phan
> (metadata driven generator for server side source code based on metadata, no
> manual coding.
Since JavaScript is a dynamic language there's no need to generate @Entity type
definitions for your model. Given a table User with id, name, and email,
you'll be able to do the following (not tie
Another suggestion: a ready-made binding between Mocha and Request:
https://npmjs.org/package/omf
Getting Mocha and Request work together is quite easy but OMF saves quite a bit
of boilerplate for you.
We use it for a current project and can't be happy!
On Jan 23, 2013, at 11:24 , John Rellis w
Another similar project: http://component.io/weepy/attr
It's a component, not the npm package but it's pretty easy to add it to your
project since it's only one file.
The API is similar to Knockout js
http://knockoutjs.com/documentation/computedObservables.html
var firstName = attr('John'), la
ch 11, 2013, Tristan Slominski wrote:
> Thanks Andrey, those are great pointers, I'll take a look.
>
> On Monday, March 11, 2013 2:08:09 PM UTC-5, Андрей Листочкин wrote:
> Another similar project: http://component.io/weepy/attr
>
> It's a component, not the npm packag
Hi, CloudBees has a CI-as-a-Service. They run Jenkins that can build
Node.JS projects.
http://www.cloudbees.com/dev.cb
On Sat, 01 Jun 2013 10:33:35 +0300, Arunoda Susiripala
wrote:
Hi,
I'm looking for a CI service like Travis CI to use with a commercial
project.
I know there is http:
Yes, and it has its own Twitter handle https://twitter.com/planetnodejs
which is very convenient.
On Thu, 13 Jun 2013 07:26:25 +0300, Luke Arduini
wrote:
looks like it's still up: planetnodejs.com
On Thu, Jun 13, 2013 at 2:45 AM, Nathan Rajlich
wrote:
Mikeal has (had?) an aggregate
Hi, Elad.
1. Node 0.12 release date.
There's no fixed release date, just like it never was with any Node
version. It's done when it's done. I.e. when all planned features are
implemented and all performance regressions are addressed. Among the three
of the following:
- features
- perfor