update docs
santiago opened this issue · comments
it is require('elasticsearch') not require('es')
No. The project is now under the es project name so when you require the
package you'll want to use es.
This changed because the elastic search people asked to have the
elasticsearch project name in npm.
On Nov 25, 2013 7:58 AM, "Santiago Gaviria" notifications@github.com
wrote:
it is require('elasticsearch') not require('es')
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/37
.
I understand, the thing is I was first looking here ...
https://npmjs.org/package/elasticsearch
But later went to the actual Github's project page where you show to do npm install es
My bad. Sorry :)
The confusion is understandable. We should npm publish a README with announcement of the move at the top.
Agreed. Sorry about the confusion @santiago.
Deprecation published as version 0.3.13 at https://npmjs.org/package/elasticsearch.