You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Pulkit Singhal <pu...@gmail.com> on 2012/06/08 18:21:29 UTC
Node.js client for CouchDB
Hello Folks,
What are some good node.js clients for communicating with CouchDB?
If you are having trouble understanding why I would even want one then just
imagine that the app will not sit as a design document inside CouchDB but
rather be elsewhere and simply talking to CouchDB via the node.js client.
Or imagine that I'm doing TDD test driven development where I want to flesh
out the user-stories and workflow as nothing more than 10 or 12 calls to
CouchDB. Now I COULD do this via curl but parsing the output from previous
JSON responses in a big test driven workflow is not exactly a joyous or
successful task for me to accomplish.
So far I've only found nano (https://github.com/dscape/nano) and I find
myself wondering why someone hasn't simply taken the javascript code that
runs Futon and dropped it into a node.js module? Has something like this
been done? Because that would (in my imaginary world) provide a full blown
client for use within node.js :)
Re: Node.js client for CouchDB
Posted by Michael Aufreiter <ma...@zive.at>.
I've adapted Tim Caswell's minimal CouchClient and use it on Substance.io.
Here's the lib and the documentation:
https://github.com/michael/couch-client
http://substance.io/michael/couch-client
Cheers,
Michael
····························································································
http://mapbox.com · http://substance.io · http://quasipartikel.at
····························································································
On Friday, June 8, 2012 at 2:26 PM, Michel Legnered wrote:
> https://github.com/felixge/node-couchdb
>
>
>
> On 8 jun 2012, at 18:21, Pulkit Singhal <pulkitsinghal@gmail.com (mailto:pulkitsinghal@gmail.com)> wrote:
>
> > Hello Folks,
> >
> > What are some good node.js clients for communicating with CouchDB?
> >
> > If you are having trouble understanding why I would even want one then just
> > imagine that the app will not sit as a design document inside CouchDB but
> > rather be elsewhere and simply talking to CouchDB via the node.js client.
> > Or imagine that I'm doing TDD test driven development where I want to flesh
> > out the user-stories and workflow as nothing more than 10 or 12 calls to
> > CouchDB. Now I COULD do this via curl but parsing the output from previous
> > JSON responses in a big test driven workflow is not exactly a joyous or
> > successful task for me to accomplish.
> >
> > So far I've only found nano (https://github.com/dscape/nano) and I find
> > myself wondering why someone hasn't simply taken the javascript code that
> > runs Futon and dropped it into a node.js module? Has something like this
> > been done? Because that would (in my imaginary world) provide a full blown
> > client for use within node.js :)
>
Re: Node.js client for CouchDB
Posted by Pulkit Singhal <pu...@gmail.com>.
Thanks Michel! Adding one more that noone's mentioned yet but I'll be very
curious if anyone else +1s it:
https://github.com/rsms/node-couchdb-min
On Fri, Jun 8, 2012 at 1:26 PM, Michel Legnered
<mi...@gmail.com>wrote:
> https://github.com/felixge/node-couchdb
>
>
>
> On 8 jun 2012, at 18:21, Pulkit Singhal <pu...@gmail.com> wrote:
>
> > Hello Folks,
> >
> > What are some good node.js clients for communicating with CouchDB?
> >
> > If you are having trouble understanding why I would even want one then
> just
> > imagine that the app will not sit as a design document inside CouchDB but
> > rather be elsewhere and simply talking to CouchDB via the node.js client.
> > Or imagine that I'm doing TDD test driven development where I want to
> flesh
> > out the user-stories and workflow as nothing more than 10 or 12 calls to
> > CouchDB. Now I COULD do this via curl but parsing the output from
> previous
> > JSON responses in a big test driven workflow is not exactly a joyous or
> > successful task for me to accomplish.
> >
> > So far I've only found nano (https://github.com/dscape/nano) and I find
> > myself wondering why someone hasn't simply taken the javascript code that
> > runs Futon and dropped it into a node.js module? Has something like this
> > been done? Because that would (in my imaginary world) provide a full
> blown
> > client for use within node.js :)
>
Re: Node.js client for CouchDB
Posted by Michel Legnered <mi...@gmail.com>.
https://github.com/felixge/node-couchdb
On 8 jun 2012, at 18:21, Pulkit Singhal <pu...@gmail.com> wrote:
> Hello Folks,
>
> What are some good node.js clients for communicating with CouchDB?
>
> If you are having trouble understanding why I would even want one then just
> imagine that the app will not sit as a design document inside CouchDB but
> rather be elsewhere and simply talking to CouchDB via the node.js client.
> Or imagine that I'm doing TDD test driven development where I want to flesh
> out the user-stories and workflow as nothing more than 10 or 12 calls to
> CouchDB. Now I COULD do this via curl but parsing the output from previous
> JSON responses in a big test driven workflow is not exactly a joyous or
> successful task for me to accomplish.
>
> So far I've only found nano (https://github.com/dscape/nano) and I find
> myself wondering why someone hasn't simply taken the javascript code that
> runs Futon and dropped it into a node.js module? Has something like this
> been done? Because that would (in my imaginary world) provide a full blown
> client for use within node.js :)
Re: Node.js client for CouchDB
Posted by Quang Van <qu...@gmail.com>.
Any good Nano vs Cradle comparisons?
I'm using cradle right now... and if a lot of people is recommending Nano
over cradle, I wonder why...
Thanks.
On Fri, Jun 8, 2012 at 1:25 PM, Mark Hahn <ma...@hahnca.com> wrote:
> > I find myself wondering why someone hasn't simply taken the javascript
> code that
> runs Futon and dropped it into a node.js module?
>
> I did something like that. I wrote a module that was a clone of jQuery
> that just implemented the ajax with http.requests. Then I made minor mods
> to the jquery code supplied with futon to make it a module. So I was able
> to write DB code that ran on the server and client with no mods.
>
> I found 3 reasons to not do this ...
>
> 1) The futon driver used a sync ajax call which was impossible to implement
> in node. I had to rewrite some of the code. The person at microsoft who
> decided to include an sync call should be shot, as well as the futon coder
> who used it.
>
> 2) The futon driver used non-standard callback returns. Different
> callbacks were used for success and error.
>
> 3) I discovered there was no benefit in my code to having the same code run
> both places.
>
> So I switched to nano. I love nano. I'm using rpc's over socket.io to get
> db access from browser.
>
Re: Node.js client for CouchDB
Posted by Mark Hahn <ma...@hahnca.com>.
The hard part is the jquery emulator. I can send you a copy of both when I
get a chance.
On Wed, Jun 13, 2012 at 6:01 AM, Pulkit Singhal <pu...@gmail.com>wrote:
> Hey Mark,
>
> Sorry for the confusion, instead of jquery.couchdb.js, I meant did you
> ever open-source your modified version of it.
>
> On Fri, Jun 8, 2012 at 2:57 PM, Mark Hahn <ma...@hahnca.com> wrote:
>
> > > The code that you modularized, rewrote and purged sync from
> >
> > It's the jquery.couchdb.js library that is included in the couchdb
> > distribution. It's not great code, but it is what futon uses.
> >
> > > What do you mean here? "no benefit in my code
> >
> > I discovered that because of security concerns I had to proxy db calls
> from
> > the browser through node. Otherwise anyone could use the same library to
> > do anything they wanted to my couchdb. If couchdb had a decent security
> > system this wouldn't be a problem. Anyway, since I had to go through
> node
> > code anyway, it was cleaner to use nano from that code than to use my
> fake
> > jquery. The proxy is a very small amount of clean code, thanks to nano's
> > simplicity.
> >
> > > I'm not sure if nano is offering authN or https
> >
> > I wouldn't know. I'm just using it on localhost. I think one of the
> > advantages of couchdb is that it is easy to run a copy on every server
> and
> > use the replication to share data across servers. So I always use
> > localhost.
> >
> > On Fri, Jun 8, 2012 at 12:13 PM, Pulkit Singhal <pulkitsinghal@gmail.com
> > >wrote:
> >
> > > Ahoy Mark! Thank you so much for validating that I'm not the 1st person
> > > ever who thought of reusing futon.
> > >
> > > Some follow-up Qs:
> > >
> > > 1) The code that you modularized, rewrote and purged sync from ...Is it
> > > available on GitHub or somewhere else in the open source community by
> any
> > > chance?
> > >
> > > 2) What do you mean here?
> > > "no benefit in my code to having the same code run both places"
> > >
> > > 3) I'm not sure if nano is offering authN or https so I'm still looking
> > > into that. I had started out rolling my own non-re-usable solution by
> > using
> > > Mikeal's request module but I wised up and am looking into Nano now.
> > Slowly
> > > but surely. Cradle's next, thanks to all the folk who pointed it out.
> > >
> > > On Fri, Jun 8, 2012 at 12:25 PM, Mark Hahn <ma...@hahnca.com> wrote:
> > >
> > > > > I find myself wondering why someone hasn't simply taken the
> > javascript
> > > > code that
> > > > runs Futon and dropped it into a node.js module?
> > > >
> > > > I did something like that. I wrote a module that was a clone of
> jQuery
> > > > that just implemented the ajax with http.requests. Then I made minor
> > > mods
> > > > to the jquery code supplied with futon to make it a module. So I
> was
> > > able
> > > > to write DB code that ran on the server and client with no mods.
> > > >
> > > > I found 3 reasons to not do this ...
> > > >
> > > > 1) The futon driver used a sync ajax call which was impossible to
> > > implement
> > > > in node. I had to rewrite some of the code. The person at microsoft
> > who
> > > > decided to include an sync call should be shot, as well as the futon
> > > coder
> > > > who used it.
> > > >
> > > > 2) The futon driver used non-standard callback returns. Different
> > > > callbacks were used for success and error.
> > > >
> > > > 3) I discovered there was no benefit in my code to having the same
> code
> > > run
> > > > both places.
> > > >
> > > > So I switched to nano. I love nano. I'm using rpc's over socket.ioto
> > > get
> > > > db access from browser.
> > > >
> > >
> >
>
Re: Node.js client for CouchDB
Posted by Pulkit Singhal <pu...@gmail.com>.
Hey Mark,
Sorry for the confusion, instead of jquery.couchdb.js, I meant did you
ever open-source your modified version of it.
On Fri, Jun 8, 2012 at 2:57 PM, Mark Hahn <ma...@hahnca.com> wrote:
> > The code that you modularized, rewrote and purged sync from
>
> It's the jquery.couchdb.js library that is included in the couchdb
> distribution. It's not great code, but it is what futon uses.
>
> > What do you mean here? "no benefit in my code
>
> I discovered that because of security concerns I had to proxy db calls from
> the browser through node. Otherwise anyone could use the same library to
> do anything they wanted to my couchdb. If couchdb had a decent security
> system this wouldn't be a problem. Anyway, since I had to go through node
> code anyway, it was cleaner to use nano from that code than to use my fake
> jquery. The proxy is a very small amount of clean code, thanks to nano's
> simplicity.
>
> > I'm not sure if nano is offering authN or https
>
> I wouldn't know. I'm just using it on localhost. I think one of the
> advantages of couchdb is that it is easy to run a copy on every server and
> use the replication to share data across servers. So I always use
> localhost.
>
> On Fri, Jun 8, 2012 at 12:13 PM, Pulkit Singhal <pulkitsinghal@gmail.com
> >wrote:
>
> > Ahoy Mark! Thank you so much for validating that I'm not the 1st person
> > ever who thought of reusing futon.
> >
> > Some follow-up Qs:
> >
> > 1) The code that you modularized, rewrote and purged sync from ...Is it
> > available on GitHub or somewhere else in the open source community by any
> > chance?
> >
> > 2) What do you mean here?
> > "no benefit in my code to having the same code run both places"
> >
> > 3) I'm not sure if nano is offering authN or https so I'm still looking
> > into that. I had started out rolling my own non-re-usable solution by
> using
> > Mikeal's request module but I wised up and am looking into Nano now.
> Slowly
> > but surely. Cradle's next, thanks to all the folk who pointed it out.
> >
> > On Fri, Jun 8, 2012 at 12:25 PM, Mark Hahn <ma...@hahnca.com> wrote:
> >
> > > > I find myself wondering why someone hasn't simply taken the
> javascript
> > > code that
> > > runs Futon and dropped it into a node.js module?
> > >
> > > I did something like that. I wrote a module that was a clone of jQuery
> > > that just implemented the ajax with http.requests. Then I made minor
> > mods
> > > to the jquery code supplied with futon to make it a module. So I was
> > able
> > > to write DB code that ran on the server and client with no mods.
> > >
> > > I found 3 reasons to not do this ...
> > >
> > > 1) The futon driver used a sync ajax call which was impossible to
> > implement
> > > in node. I had to rewrite some of the code. The person at microsoft
> who
> > > decided to include an sync call should be shot, as well as the futon
> > coder
> > > who used it.
> > >
> > > 2) The futon driver used non-standard callback returns. Different
> > > callbacks were used for success and error.
> > >
> > > 3) I discovered there was no benefit in my code to having the same code
> > run
> > > both places.
> > >
> > > So I switched to nano. I love nano. I'm using rpc's over socket.io to
> > get
> > > db access from browser.
> > >
> >
>
Re: Node.js client for CouchDB
Posted by Mark Hahn <ma...@hahnca.com>.
> The code that you modularized, rewrote and purged sync from
It's the jquery.couchdb.js library that is included in the couchdb
distribution. It's not great code, but it is what futon uses.
> What do you mean here? "no benefit in my code
I discovered that because of security concerns I had to proxy db calls from
the browser through node. Otherwise anyone could use the same library to
do anything they wanted to my couchdb. If couchdb had a decent security
system this wouldn't be a problem. Anyway, since I had to go through node
code anyway, it was cleaner to use nano from that code than to use my fake
jquery. The proxy is a very small amount of clean code, thanks to nano's
simplicity.
> I'm not sure if nano is offering authN or https
I wouldn't know. I'm just using it on localhost. I think one of the
advantages of couchdb is that it is easy to run a copy on every server and
use the replication to share data across servers. So I always use
localhost.
On Fri, Jun 8, 2012 at 12:13 PM, Pulkit Singhal <pu...@gmail.com>wrote:
> Ahoy Mark! Thank you so much for validating that I'm not the 1st person
> ever who thought of reusing futon.
>
> Some follow-up Qs:
>
> 1) The code that you modularized, rewrote and purged sync from ...Is it
> available on GitHub or somewhere else in the open source community by any
> chance?
>
> 2) What do you mean here?
> "no benefit in my code to having the same code run both places"
>
> 3) I'm not sure if nano is offering authN or https so I'm still looking
> into that. I had started out rolling my own non-re-usable solution by using
> Mikeal's request module but I wised up and am looking into Nano now. Slowly
> but surely. Cradle's next, thanks to all the folk who pointed it out.
>
> On Fri, Jun 8, 2012 at 12:25 PM, Mark Hahn <ma...@hahnca.com> wrote:
>
> > > I find myself wondering why someone hasn't simply taken the javascript
> > code that
> > runs Futon and dropped it into a node.js module?
> >
> > I did something like that. I wrote a module that was a clone of jQuery
> > that just implemented the ajax with http.requests. Then I made minor
> mods
> > to the jquery code supplied with futon to make it a module. So I was
> able
> > to write DB code that ran on the server and client with no mods.
> >
> > I found 3 reasons to not do this ...
> >
> > 1) The futon driver used a sync ajax call which was impossible to
> implement
> > in node. I had to rewrite some of the code. The person at microsoft who
> > decided to include an sync call should be shot, as well as the futon
> coder
> > who used it.
> >
> > 2) The futon driver used non-standard callback returns. Different
> > callbacks were used for success and error.
> >
> > 3) I discovered there was no benefit in my code to having the same code
> run
> > both places.
> >
> > So I switched to nano. I love nano. I'm using rpc's over socket.io to
> get
> > db access from browser.
> >
>
Re: Node.js client for CouchDB
Posted by Pulkit Singhal <pu...@gmail.com>.
Ahoy Mark! Thank you so much for validating that I'm not the 1st person
ever who thought of reusing futon.
Some follow-up Qs:
1) The code that you modularized, rewrote and purged sync from ...Is it
available on GitHub or somewhere else in the open source community by any
chance?
2) What do you mean here?
"no benefit in my code to having the same code run both places"
3) I'm not sure if nano is offering authN or https so I'm still looking
into that. I had started out rolling my own non-re-usable solution by using
Mikeal's request module but I wised up and am looking into Nano now. Slowly
but surely. Cradle's next, thanks to all the folk who pointed it out.
On Fri, Jun 8, 2012 at 12:25 PM, Mark Hahn <ma...@hahnca.com> wrote:
> > I find myself wondering why someone hasn't simply taken the javascript
> code that
> runs Futon and dropped it into a node.js module?
>
> I did something like that. I wrote a module that was a clone of jQuery
> that just implemented the ajax with http.requests. Then I made minor mods
> to the jquery code supplied with futon to make it a module. So I was able
> to write DB code that ran on the server and client with no mods.
>
> I found 3 reasons to not do this ...
>
> 1) The futon driver used a sync ajax call which was impossible to implement
> in node. I had to rewrite some of the code. The person at microsoft who
> decided to include an sync call should be shot, as well as the futon coder
> who used it.
>
> 2) The futon driver used non-standard callback returns. Different
> callbacks were used for success and error.
>
> 3) I discovered there was no benefit in my code to having the same code run
> both places.
>
> So I switched to nano. I love nano. I'm using rpc's over socket.io to get
> db access from browser.
>
Re: Node.js client for CouchDB
Posted by Mark Hahn <ma...@hahnca.com>.
> I find myself wondering why someone hasn't simply taken the javascript
code that
runs Futon and dropped it into a node.js module?
I did something like that. I wrote a module that was a clone of jQuery
that just implemented the ajax with http.requests. Then I made minor mods
to the jquery code supplied with futon to make it a module. So I was able
to write DB code that ran on the server and client with no mods.
I found 3 reasons to not do this ...
1) The futon driver used a sync ajax call which was impossible to implement
in node. I had to rewrite some of the code. The person at microsoft who
decided to include an sync call should be shot, as well as the futon coder
who used it.
2) The futon driver used non-standard callback returns. Different
callbacks were used for success and error.
3) I discovered there was no benefit in my code to having the same code run
both places.
So I switched to nano. I love nano. I'm using rpc's over socket.io to get
db access from browser.
Re: Node.js client for CouchDB
Posted by Morgan Craft <mg...@gmail.com>.
To my understanding Nano is just a light wrapper around Mikeal's request,
I've yet to use Nano, but I use Mikeal's request for various projects.
I had nothing against cradle and at the time it was the only lib.
On Fri, Jun 8, 2012 at 12:43 PM, Sam Bisbee <sa...@sbisbee.com> wrote:
> Nano is the most popular, cradle seems to be less popular, and
> saggingcouch.com gives you JS in browser and node with a mirrored API in
> PHP (I wrote sag so am biased).
>
> Or just use a straight HTTP lib like Mikeal's request.
>
> Cheers,
>
> --
> Sam Bisbee
> Sent from my phone so please excuse brevity and typos.
> On Jun 8, 2012 9:21 AM, "Pulkit Singhal" <pu...@gmail.com> wrote:
>
> > Hello Folks,
> >
> > What are some good node.js clients for communicating with CouchDB?
> >
> > If you are having trouble understanding why I would even want one then
> just
> > imagine that the app will not sit as a design document inside CouchDB but
> > rather be elsewhere and simply talking to CouchDB via the node.js client.
> > Or imagine that I'm doing TDD test driven development where I want to
> flesh
> > out the user-stories and workflow as nothing more than 10 or 12 calls to
> > CouchDB. Now I COULD do this via curl but parsing the output from
> previous
> > JSON responses in a big test driven workflow is not exactly a joyous or
> > successful task for me to accomplish.
> >
> > So far I've only found nano (https://github.com/dscape/nano) and I find
> > myself wondering why someone hasn't simply taken the javascript code that
> > runs Futon and dropped it into a node.js module? Has something like this
> > been done? Because that would (in my imaginary world) provide a full
> blown
> > client for use within node.js :)
> >
>
Re: Node.js client for CouchDB
Posted by Sam Bisbee <sa...@sbisbee.com>.
Nano is the most popular, cradle seems to be less popular, and
saggingcouch.com gives you JS in browser and node with a mirrored API in
PHP (I wrote sag so am biased).
Or just use a straight HTTP lib like Mikeal's request.
Cheers,
--
Sam Bisbee
Sent from my phone so please excuse brevity and typos.
On Jun 8, 2012 9:21 AM, "Pulkit Singhal" <pu...@gmail.com> wrote:
> Hello Folks,
>
> What are some good node.js clients for communicating with CouchDB?
>
> If you are having trouble understanding why I would even want one then just
> imagine that the app will not sit as a design document inside CouchDB but
> rather be elsewhere and simply talking to CouchDB via the node.js client.
> Or imagine that I'm doing TDD test driven development where I want to flesh
> out the user-stories and workflow as nothing more than 10 or 12 calls to
> CouchDB. Now I COULD do this via curl but parsing the output from previous
> JSON responses in a big test driven workflow is not exactly a joyous or
> successful task for me to accomplish.
>
> So far I've only found nano (https://github.com/dscape/nano) and I find
> myself wondering why someone hasn't simply taken the javascript code that
> runs Futon and dropped it into a node.js module? Has something like this
> been done? Because that would (in my imaginary world) provide a full blown
> client for use within node.js :)
>
Re: Node.js client for CouchDB
Posted by Stephan Bardubitzki <st...@bardubitzki.com>.
+1 for cradle
On 12-06-08 09:25 AM, Morgan Craft wrote:
> I haven't messed with couchdb much lately, but when I was experimenting
> with it and nodejs I was using the cradle library. However, on the nodeup
> podcast everyone seems to recommend Nano as the preferred couchdb lib as of
> now.
>
> -m
>
>
>
> On Fri, Jun 8, 2012 at 12:21 PM, Pulkit Singhal<pu...@gmail.com>wrote:
>
>> Hello Folks,
>>
>> What are some good node.js clients for communicating with CouchDB?
>>
>> If you are having trouble understanding why I would even want one then just
>> imagine that the app will not sit as a design document inside CouchDB but
>> rather be elsewhere and simply talking to CouchDB via the node.js client.
>> Or imagine that I'm doing TDD test driven development where I want to flesh
>> out the user-stories and workflow as nothing more than 10 or 12 calls to
>> CouchDB. Now I COULD do this via curl but parsing the output from previous
>> JSON responses in a big test driven workflow is not exactly a joyous or
>> successful task for me to accomplish.
>>
>> So far I've only found nano (https://github.com/dscape/nano) and I find
>> myself wondering why someone hasn't simply taken the javascript code that
>> runs Futon and dropped it into a node.js module? Has something like this
>> been done? Because that would (in my imaginary world) provide a full blown
>> client for use within node.js :)
>>
> --------------------------------
> Spam/Virus scanning by CanIt Pro
>
> For more information see
> http://www.kgbinternet.com/SpamFilter.htm
>
> To control your spam filter, log in at
> http://filter.kgbinternet.com
>
Re: Node.js client for CouchDB
Posted by Pulkit Singhal <pu...@gmail.com>.
Interesting comment about nodeup, so far I found one that has the nano
author:
http://nodeup.com/eleven
Any other podcasts that mention nano?
On Fri, Jun 8, 2012 at 11:25 AM, Morgan Craft <mg...@gmail.com> wrote:
> I haven't messed with couchdb much lately, but when I was experimenting
> with it and nodejs I was using the cradle library. However, on the nodeup
> podcast everyone seems to recommend Nano as the preferred couchdb lib as of
> now.
>
> -m
>
>
>
> On Fri, Jun 8, 2012 at 12:21 PM, Pulkit Singhal <pulkitsinghal@gmail.com
> >wrote:
>
> > Hello Folks,
> >
> > What are some good node.js clients for communicating with CouchDB?
> >
> > If you are having trouble understanding why I would even want one then
> just
> > imagine that the app will not sit as a design document inside CouchDB but
> > rather be elsewhere and simply talking to CouchDB via the node.js client.
> > Or imagine that I'm doing TDD test driven development where I want to
> flesh
> > out the user-stories and workflow as nothing more than 10 or 12 calls to
> > CouchDB. Now I COULD do this via curl but parsing the output from
> previous
> > JSON responses in a big test driven workflow is not exactly a joyous or
> > successful task for me to accomplish.
> >
> > So far I've only found nano (https://github.com/dscape/nano) and I find
> > myself wondering why someone hasn't simply taken the javascript code that
> > runs Futon and dropped it into a node.js module? Has something like this
> > been done? Because that would (in my imaginary world) provide a full
> blown
> > client for use within node.js :)
> >
>
Re: Node.js client for CouchDB
Posted by Morgan Craft <mg...@gmail.com>.
I haven't messed with couchdb much lately, but when I was experimenting
with it and nodejs I was using the cradle library. However, on the nodeup
podcast everyone seems to recommend Nano as the preferred couchdb lib as of
now.
-m
On Fri, Jun 8, 2012 at 12:21 PM, Pulkit Singhal <pu...@gmail.com>wrote:
> Hello Folks,
>
> What are some good node.js clients for communicating with CouchDB?
>
> If you are having trouble understanding why I would even want one then just
> imagine that the app will not sit as a design document inside CouchDB but
> rather be elsewhere and simply talking to CouchDB via the node.js client.
> Or imagine that I'm doing TDD test driven development where I want to flesh
> out the user-stories and workflow as nothing more than 10 or 12 calls to
> CouchDB. Now I COULD do this via curl but parsing the output from previous
> JSON responses in a big test driven workflow is not exactly a joyous or
> successful task for me to accomplish.
>
> So far I've only found nano (https://github.com/dscape/nano) and I find
> myself wondering why someone hasn't simply taken the javascript code that
> runs Futon and dropped it into a node.js module? Has something like this
> been done? Because that would (in my imaginary world) provide a full blown
> client for use within node.js :)
>