dependencies because it will make it easier to port it onto Parse.com as a
cloud module. The more dependencies and/or files involved, the messier it
looks when bringing in an existing npm module to an environment like Parse.
So far I'm inclined to use node-elasticsearch-clienthttps://github.com/phillro/node-elasticsearch-client/because it has no dependencies according to its
The official elasticsearch-jshttps://github.com/elasticsearch/elasticsearch-jsclient on the other hand has four other runtime dependencies.
If there is already a branch for this client that's more suited to porting
for environments like Parse.com, can someone chime in and let me know about
I'm partially inclined to just use nothing but a simple HTTP request, in
order to be lean, but I thought it might be worth exploring if I could go
Please feel free to share your thoughts and pointers.
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5db855f6-d8a1-40ee-8c20-8fb72a3848ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.