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

@lieberweiss/http-service

v0.0.2

Published

[![tested with mocha](https://img.shields.io/badge/tested_with-mocha-99424f.svg?style=flat-square)](https://github.com/mochajs/mocha)

Downloads

1

Readme

lieberweiss_module_service

tested with mocha

Summary

I. Release a new version

  • Run yarn build
  • Run yarn new-version
  • Run yarn publish
  • Commit and push changes

II. Installation

Run npm install @lieberweiss/service

To import the lib, use const service = require('@lieberweiss/service.

III. Usage

The service function takes 3 mandatory parameters :

  • serviceName (type: String)
  • url (type: String)
  • commands (type: Object)

It returns a function which can be used to call an API, taking 3 parameters :

  • command (type: String)
  • args (type: Object)
  • auth (type: Function, optional)
  • files (type:Array, optional)

files is used when one want to post files. files object array contains the following object : {name, originalFilename, rs}:

  • name is the fieldname of the file (default to file)
  • originalFilename orginal filename of the file
  • rs is a of type <fs.ReadStream>

For a full implementation, see mock-service.js

IV. Command props

Each command has 2 mandatory props:

  • route (type: String | Function)
  • method (type: String, enum: ['GET', 'POST', 'DELETE', 'PUT'])

When route is a function, service will call the function and pass three arguments : args, auth, files.

You can also provide optional parameters:

  • query (type: Array[String | Array[String]]) : every String queryParam then becomes required, unless you provide an Array instead of a String (e.g: ['queryParam', 'o']
  • body: (type: Array[String | Array[String]]) : every String bodyParam then becomes required, unless you provide an Array instead of a String (e.g: ['bodyParam', 'o']
  • stream (type: Boolean, default: false): if true, the response is returned without being processed, otherwise you will receive a json processed response
  • withStatus (type: Boolean, default: false): if true, the response will be an Object { status, payload }, with payload containing the returned response data
  • errorField (type: String, default: 'message'): The field to use in the response in case of error.