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

service-fetch

v0.1.6

Published

Promise Based wrapper for any Swagger defined API.

Downloads

4

Readme

service-fetch

Promise Based wrapper for any Swagger defined API.

Installation

service-fetch can be installed directly through npm:

$ npm install --save service-fetch

Usage

Here is an example definition of a potential path in your Swagger Doc:

  /user/login:
    get:
      description: Performs a login request
      tags: [ user ]
      operationId: login

      security: []

      responses:
        "200":
          description: Success
          schema:
            $ref: "#/definitions/Response"
        default:
          description: Error
          schema:
            $ref: "#/definitions/Response"

Here is how you can import your Swagger Doc and perform API operations using simple services:


// Setup and load your Swagger API Definition, your namespaces are considered services
import { loadServices, getServices } from 'service-fetch';

// Importing the Swagger Doc definition of your API
import api from "./api.js";

// Use the loadServices helper function to initialize the API
loadServices({
	apiDpc: api,
	host: "http://localhost:3001/api"
});

// ...

// Once you've loaded the Swagger Doc and the services within, you can consider your Swagger namespaces as services and you can call upon their operations as needed.

const { UserService } = getServices();

let username = "[email protected]";
let password = "my-special-password";

// UserService.login() translates to a POST request to the /api/user/login endpoint
let { data, error } = await UserService.login({ body: { username, password } }); 

// Perform any UI operations necessary using the data and error returned values...

Contribute

$ git clone https://github.com/DemandHub/service-fetch.git
$ npm install

... make code changes in ./src

$ npm run compile