npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

elastics

v0.3.0

Published

Simple & handy client for elasticsearch

Downloads

5

Readme

elastics

Simple & handy client for elasticsearch. It's just wrapper around http.request with shortcuts for elasticsearch.

It implements all available functionality & even upcoming.

Be careful wile using settings for default type & index: they are client's instance variables. So if you are going to have one client in an application you'd better set them explicitly in each call. JS is so asynchronus...

usage

Elastics = require 'elastics'
es = new Elastics
  host:  hostname # default 'localhost'
  port:  port     # default 9200
  index: index    # default null
  type:  type     # default null

This params are stored in es.defaults. You can change them wi

  • setIndex(index, [type = null])
  • setType(type)

For the first time I've made all the methods adaptive to arguments. But then there have appeared to much significant arguments so I gave it up.

So all the methods take two args: object with parameters & callback. For now you can omit callback but not params.

params fields:

  • method - http request method
  • index
  • type
  • path - last part for url
  • id - same as path but with higher priority
  • query - query string for url. you can set routing params here
  • data - request body

You can omit fields stored in defaults

lowest level

request(params, [callback])

request-type level

get(), put(), post(), delete() - just set the method

highest level

  • putMapping() - put with path = '_mapping'
  • search() - post with path = '_search'
  • index() - if id field is set then put else post

few examples

es.setType()
# index:null, type: null

es.get {}
# GET http://host::port/

es.post {index: 'index'}
# POST http://host::port/index 

es.setIndex 'other_index', 'type
mapping =
  type:
    fields:
      field_one: type: 'string'
es.putMapping {data: mapping}
# PUT http://host::port/other_index/type
# body is json of mapping

es.get {index: 'one', type: 'two', id: 'three'}
# GET http://host::port/one/two/three

see tests

LICENSE

BSD