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

@apicase/adapter-fetch

v0.15.1

Published

Fetch adapter for Apicase

Downloads

1,042

Readme

@apicase/adapter-fetch

Fetch adapter for @apicase/core

Installation

  1. Install via NPM
npm install @apicase/adapter-fetch
  1. Import it
import { apicase } from '@apicase/core'
import fetch from '@apicase/adapter-fetch'

const fetchAPI = apicase(fetch)

We use node-fetch as polyfill for Node.js

Basic usage

const req = await fetchAPI({
  url: '/api/posts',
  headers: { token: 'my_secret_token' },
  query: { userId: 1 }
})

// Whether request was succeed or failed
console.log(req.success)

// Fetch result (with response body, headers etc)
console.log(req.result)

Features

Url params

Fetch adapter has path-to-regexp to pass urls params smarter.
Params are stored in params property

fetchAPI({
  url: '/api/posts/:id',
  params: { id: 1 }
})
// => GET /api/posts/1

Query params

You can define query params in query property

fetchAPI({
  url: '/api/posts',
  query: { userId: 1 }
})
// => GET /api/posts?userId=1

Status validation

If you have some specific API, you can define custom status validation

fetchAPI({
  url: '/api/posts',
  validateStatus: status => status === 200
})

Default status validation behaviour is:

function(status) {
  return status >= 200 && status < 300
}

Url concatenation in services

Extended services will have concatenated URI, if the next part doesn't start with /:

const service1 = new ApiService(fetch, { url: '/api' })

// { "url": "/api/posts" }
const service2 = service1.extend({ url: 'posts' })

// { "url": "/posts" }
const service3 = service1.extend({ url: '/posts' })

Full payload params list

{
  // Request URL
  "url": String,
  // Response parser
  // default: 'json'
  "parser": String,
  // Request method
  // default: 'GET'
  "method": String,
  // Request headers
  // default: {}
  "headers": Object,
  // Request body
  // default: undefined
  "body": Object|FormData,
  // Credentials
  // default: 'omit'
  "credentials": String,
  // URL params
  // default: {}
  "params": Object,
  // Query params
  // default: {}
  "query": Object,
  // Status validation callback
  // default: status => status >= 200 && status < 300
  "validateStatus": Function
}

Author

Anton Kosykh

License

MIT