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

fetch-on-rest

v2.0.4

Published

A REST API wrapper around window.fetch

Downloads

51

Readme

Fetch-on-REST

Build Status

Fetch-on-REST is a RESTful API wrapper built around window.fetch.

GitHub provides a polyfill for fetch to work on all browsers. Fetch is also available on react-native by default.

This wrapper is intended to work on both the browsers as well as with react-native.

Usage

Using Fetch-on-REST is as simple as passing the data and handling the JSON response. Headers are automatically set to accept JSON and the responses are json objects.

var Rest = require('fetch-on-rest');
var api = new Rest('/api/v2');

api.get('users', {name: 'foo'}).then(function(response) {});
// GET request on '/api/v2/users?name=foo'

api.post('posts', {title: 'foo', content: 'bar'}).then(function(response) {});
// POST request on '/api/v2/posts' with data {"title": "foo", "content": "bar"}

API

Initialization

new Rest(basePath="/", addOptions=function() {}, useTrailingSlashes=false):

basePath: Is a string. Can be absolute or relative path.

addOptions(defaultOptions, url): Is an optional function. Can be used to modify the headers. Should modify the received defaultOptions object and not return a new object.

useTrailingSlashes: Default false. By setting true, .get('users') will hit the url /users/.

Example of addOptions:

// Adding same-origin and X-CSRFToken token
function addOptions(defaults, url) {
  defaults.credentials = 'same-origin';
  if(defaults.method != 'get')
    defaults.headers['X-CSRFToken'] = 'AUTHTOKENX';
}

var useTrailingSlashes = true;
var api = new Rest('/', addOptions, useTrailingSlashes);

Requests

.get(segments, query)

.post(segments, data, query)

.put(segments, data, query)

.patch(segments, data, query)

.del(segments, query)

.rawGet(segments, query)

All requests return a promise object. The promise object resolves to JSON response (except rawGet which resolves to text). URL parsing is handled using the exhaustive URI.js library.

segments: segments are the parts of url. Can be array or string.

query: query is the search or GET params part of the url. Should be a key-value object.

data: data is the json body to be sent in the request.

Changelog and Migration

Since version 2:

  • the delete method has been renamed as del
  • have dropped the babel and ES2015 dependencies: this makes usage with React Native smoother

Contribution

Though we intend to keep the library minimalistic, we would love to see the pull-requests and discuss new issues.

Thanks for checking it out.