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

mir-client

v5.0.0

Published

A Mir API Client

Downloads

15

Readme

Mir Client

Mir is a framework that provides both an API that can be accessed by front-end client applications and an admin dashboard for managing data associated with the particular API instance. APIs associated with Mir should be accessed using the Mir client library.

The Mir client is a Javascript library designed to abstract away most of the API functionality making it easy for the front-end developer to access the data without having to worry about the specifics of the HTTP request.

Using the client

First add the client to the project: npm install --save mir-client

The client can then be imported into the project. For example, in the following code snippet we will get data from an 'applicator' collection:

import mir from 'mir-client'

var api_url = 'http://some-api.whatever.com'

// Create a main API Client
var api_client = mir(api_url)
var resource = api_client('resourceName')

function get_applicator_data() {
  return resource.get().send().then((result) => {
    return result
  })
}

This should return a response that has a structure like this:

{
  config: {...},
  data: {...},
  headers: {...},
  request: {...},
  status: 200,
  statusText: "OK"
}

The data object within this request will have the relevant data from the API. This data object will have a structure like this:

{
  _items: [...],
  _links: {...},
  _meta: {...}
}

The _items array will contain an array of the actual data objects. _links will probably never be used in front-end development.

The _meta object within data will contain information about the request. It will have a structure like this:

{
  max_results: 25,
  page: 1,
  total: 2
}

Client functions

The client can be used to perform any standard REST actions.

GET

// the .get() function is used to make a GET request
resource.get().send().then((result) => {
  return result
}

GET ONE

// the .getOne() function takes an id parameter
// it should be used to get one resource by its id
var existing_applicator_id = '1234'

resource.getOne(existing_applicator_id).send().then((result) => {
  return result
}

POST

// the .post() function takes params of the targeted collection and the payload
// it should be used to make a POST request--i.e. to create a new resource
var new_applicator_object = {
  'business_name': 'Some Guy Inc.',
  'phone': '867-5309',
  'zip_code': '10001'
}

resource.post(new_applicator_object).send().then((result) => {
  return result
}

PATCH

// the .patch() function takes params of the targeted collection and the payload
// it should be used to make a PATCH request--i.e. to update an existing resource
var update_this_id = '1234'
var applicator_update_object = {
  'business_name': 'Some Other Guy Inc.'
}

resource.patch(update_this_id, applicator_update_object).send().then((result) => {
  return result
})

DELETE

// the .deleteOne() function takes params of the targeted collection and the id
// it should be used to make a DELETE request in order to delete one resource by its id
var delete_this_id = '1234'

resource.deleteOne(delete_this_id).send().then((result) => {
    return result
})

Additional functions

Some of the REST functions have additional functions that can be chained to them. All functions include a .send() function. This function actually makes the request and returns a node.js promise. Every request must call .send() in order to actually make a request and return data. GET and GET ONE both include initial filtering functions. POST and PATCH, at this time, do not support additional filtering.

GET

projection -- takes a property and either true/false as parameters. Allows for specifying whether to return only certain values .projection('name', true) or to exclude certain values .projection('name', false). sort -- takes a property and either +/- as parameters. Allows for returning results sorting either ascending .sort('name', '+') or descending .sort('name', '-'). filter -- takes a MongoDB query object that can be used to specify which objects should be returned in the result. For more information on this, refer to How to Query MongoDB. page -- takes a number and returns that page of the specified request .page(3). limit -- takes a number and updates the max_results parameter for the request .limit(50). next -- returns the next page, will only work if an initial request has been made. previous -- returns the previous page, will only work if an initial request has been made. first -- returns the first page, will only work if an initial request has been made. last-- returns the last page, will only work if an initial request has been made. send-- sends the request.

Example:

resource.get()
  .filter(
    {
      'resource_name': 'My Resource',
      'resource_date': {'$gt': 'Wed, 06 Jun 2018 14:52:37 GMT'}
    }
  )
  .sort('resource_date', '-')
  .send()
  .then((result) => {
    return result
  }

GET ONE

projection -- takes a property and either true/false as parameters. Allows for specifying whether to return only certain values .projection('name', true) or to exclude certain values .projection('name', false). send-- sends the request.

For more detail about how these functions interact with the API code, the Eve documentation can be consulted.