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

@xtreamr/cla-request

v1.0.5

Published

``` yarn add @xtreamr/cla-request //or npm install @xtreamr/cla-request --save-dev ```

Downloads

3

Readme

Install

yarn add @xtreamr/cla-request 
//or
npm install @xtreamr/cla-request --save-dev

Use:

import Request from '@xtreamr/cla-request'

export const request = new Request()

request.init({ apiUrl: 'www.someapiurl.com' })
request.setBearer({ bearer: 'auth-token' }) // set as authorization header

// - Path: path to build the final end point with apiUrl. If path is: /product/1 -> www.someapiurl.com/product/1
// - Options: same options as vanilla fetch: https://developer.mozilla.org/es/docs/Web/API/Fetch_API
// with some changes. Body should be an object and 'application/json' is used as default content type header. If you prefer use a formData pass a formData key that will be set as body internaly (you can use both at same time: body and formData)
// Add two new options to cache responses: cache and refreshCache (to force refresh cache data).
request.fetch(path, options)

To mock data into development you could configure the request with two paremeters into constructor:

const mockData = {
  // use query, parameters and optionsFetch to mock the api
  // use async functions to not include this code into the final bundle
  '/product/{id}': async ({ 
    query, // query parameters 
    parameters, // path parameters (id in this case), show path '/product/{id}' into mockOptions
    optionsFetch // fetch options { method, mode, headers, body...} https://developer.mozilla.org/es/docs/Web/API/Fetch_API/Using_Fetch
  }) => {
    return {
      id: 1,
      name: 'tv'
    }
  },
  '/products': async () => {
    return [
      {
        id: 1,
        name: 'tv'
      },
      {
        id: 2,
        name: 'computer'
      }
    ]
  },
}

const mockOptions = {
    disabled: false, // if is disable the rest of keys haven't any effect
    delay: 10, // delay of response
    all: false, // all path mock = true
    paths: { // to enable or disable by path
      '/product/{id}': true, // enabled
      '/products': false, // disabled
    },
  },

export const request = new Request({
  mockData, 
  mockOptions
})