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

crest-js

v1.1.0

Published

Javascript client for REST APIs

Downloads

2

Readme

crest-js

Crest JS is a small and friendly Client for REST APIs. Unlike most HTTP clients out there, Crest does not accept URLs as strings. URLs are instead constructed with Javascript Proxies and an opinionated convention for method names. This makes your code more readable as you no longer have to understand the complex string shuffling commonly associated with building URLs.

Inspired by this medium article

Check out the awesome examples below

const { crest } = require('crest-js');

// Let's play with a contrived API for a database of companies and their staff
const api = crest({ baseUrl: 'https://api.example.com' })
  .authorizationBasic('your-secret-here');

Let's try a simple HTTP request

api
  .getCompaniesBranches('11335577')
  // translates to: GET /companies/11335577/branches

  .then((branches) => {
    console.log(', '.join(branches.map((branch) => branch.location)));
  });

Now let's update the location for a company branch

api
  .putCompaniesBranches('11335577', '2468', {json: {location: '186 1st Avenue, NY'} })
  // translates to: PUT /companies/11335577/branches/2468
  // payload:       { "location": "186 1st Avenue, NY" }

And finally let's send a reminder to all staff accounts from a company branch.

const the_message = 'Remember to announce your time off before EOB today.';
api
  .getCompaniesStaff('11335577', {branch_id: '2468'})
  // translates to: GET /companies/11335577/staff?branch_id=2468
  
  .then((staff) => {
    return Promise.all(staff.map((member) => {

      return api.postCompaniesStaffMessages('11335577', member.id, {json: {message: the_message}});
      // translates to: POST /companies/11335577/staff/{id}/messages
      // payload:       { "message": "Remember to announce..." }

    }))
    .then(() => {
      console.log('Message sent.');
    });
  });

Alternatively we could do something with the github API using async/await

const github = crest({ baseUrl: 'https://api.github.com' })
  .authorizationBasic('your-secret-here');

const orgs = await github.getUsersOrgs('MihaiBalint');
// translates to: GET /users/MihaiBalint/orgs

const repos = await github.getUsersRepos('MihaiBalint');
// translates to: GET /users/MihaiBalint/repos

// POST /authorizations
const auth = await github.postAuthorizations({ json: { 'scopes': ['public_repo'] } });
// translates to: POST /authorizations
// payload:       { "scopes": ["public_repo"] }

So what actually happened there? Crest converts camel-case method names to URLs and interpolates method arguments to obtain the url path. Query parameters and request payloads are added using dict arguments.

Custom request headers

When you need to send some proproetary headers with every request, you could do the following:

const github = crest({ baseUrl: 'https://proprietary-api.example.com' })
  .setCustomHeaders({ 'X-Custom-Header': 'your-proprietary-value' });

const bits = await github.getBits('proprietary');
// translates to: GET /bits/proprietary with http headers:
// X-Custom-Header: your-proprietary-value

Installation

node:

$ npm install crest-js

Running node tests

Install dependencies:

$ npm install
$ npm test

License

MIT