API has changed, but more powerful

.gitignore

@@ -1,2 +1,32 @@
-.DS_Store
+# Logs
+logs
+*.log
+
+# Runtime data
+pids
+*.pid
+*.seed
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+
+# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Compiled binary addons (http://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directory
+# Deployed apps should consider commenting this line out:
+# see https://npmjs.org/doc/faq.html#Should-I-check-my-node_modules-folder-into-git
 node_modules
+
+# Ignore .env configuration files
+.env
+
+# Ignore .DS_Store files on OS X
+.DS_Store
+.idea

.travis.yml

@@ -1,14 +1,8 @@
 language: node_js
 
 node_js:
-  - 0.11
   - 0.10
-  - 0.8
 
 services:
   - mongodb
   - elasticsearch
-
-notifications:
-  email:
-    - james.r.carr@gmail.com

CHANGELOG.md

@@ -0,0 +1,12 @@
+## 2.0.0 (2014-10-10)
+
+Features:
+
+- Moved to [official elasticsearch driver](https://github.com/elasticsearch/elasticsearch-js)
+	- Caused `search` api to conform closer to official driver
+	- Added options to searching
+- Refactored bulk api
+- Refreshed README.md
+- Added CHANGELOG.md
+- Added CONTRIBUTING.md
+- Added LICENSE.md

CONTRIBUTING.md

@@ -0,0 +1,53 @@
+# Contributing
+Pull requests are always welcome as long as an accompanying test case is
+associated. 
+
+This project is configured to use [git
+flow](https://github.com/nvie/gitflow/) and the following conventions
+are used:
+
+* ``develop`` - represents current active development and can possibly be
+  unstable. 
+* ``master`` - pristine copy of repository, represents the currently
+  stable release found in the npm index.
+* ``feature/**`` - represents a new feature being worked on
+
+If you wish to contribute, the only requirement is to: 
+
+- branch a new feature branch from develop (if you're working on an
+  issue, prefix it with the issue number)
+- make the changes, with accompanying test cases
+- issue a pull request against develop branch
+
+Although I use git flow and prefix feature branches with "feature/" I
+don't require this for pull requests... all I care is that the feature
+branch name makes sense. 
+
+Pulls requests against master or pull requests branched from master will
+be rejected.
+
+## Examples
+Someone picks up issue #39 on selective indexing.
+
+Good branch names:
+* 39-selective-indexing
+* feature/39-selective-indexing
+
+Someone submits a new feature that allows shard configuration:
+
+Good branch names:
+* feature/shard-configuration
+* shard-configuration
+* or file an issue, then create a feature branch
+
+Feel free to ping me if you need help! :)
+
+## Running Tests
+In order to run the tests you will need:
+
+* An elasticsearch server running on port 9200
+* A mongodb server
+* [mocha](http://visionmedia.github.com/mocha/)
+
+With those installed, running ''npm test'' will run the tests with the
+preferred timeout (which is extended for integration tests. 

LICENSE.md

@@ -0,0 +1,9 @@
+[The MIT License](https://tldrlegal.com/l/mit)
+
+Copyright (c) 2012 James R. Carr <james.r.carr@gmail.com>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.