in functionality is buggy.

[jperkelens]

Example:
{ 'field1.equals' : val, 'field2.in: [val2, val3] } will produce 'SELECT * from table where field1 = $1 AND field2 IN ($1, $2, $3)

[backhand]

I've uncovered this bug as well - a workaround is to place the in/nin predicate first, i.e. like this:
{ 'field2.in: [val2, val3], 'field1.equals' : val }

The bug is caused by the utils.quote function which doesn't take into account that previous outValues are "taken" by previous operators. By placing the in/nin predicate first, the outValues correspond to the values actually meant for that operator. This probably won't make sense unless you check the actual code - see statements.js:buildOperator and utils.js:quote :)

[thadclay]

Fixed in #48