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

exovision

v1.0.3

Published

Call remote HTTP services in an easy way, both in brwoser and node.js

Downloads

10

Readme

ExoVision

Call remote HTTP RESTful services in easy way, both in browser and Node.js.

import exovision from 'exovision' // const exovision = require('exovision').default

// using process.ENV
const myRemoteService = exovision('MY_REMOTE_SERVICE') // process.env.MY_REMOTE_SERVICE === https://myremoteservice.com

// or using uri
const myRemoteService2 = exovision('https://myremoteservice.com')

// now we have 4 methods
myRemoteService.get()
myRemoteService.post()
myRemoteService.put()
myRemoteService.del()

All methods have same signature:

type ExovisionBoundTransmit = (
  path: string, // path to add on baseurl, eg. /rabbids
  data?: any, // can be any POJO: if the method is get, it will be transformed to querystring otherwise to body
  options?: ITransmissionOptions, // see below
) => Promise<any>

This is ITransmissionOptions interface:

interface ITransmissionOptions {
  contentType?: string // defaults to 'application/json'
  responseType?: string // defaults to 'json'
  transcodeResponse?<O, T>(data: O): T | Promise<T>
  echoCall?: boolean // simulates the call and returns request (for testing and debugging)
  token?: string // bearer login token, added to headers['Authorization'] = `Bearer ${token}`
}

transcodeResponse: custom transformation function. For example, if you need to convert xml to json you can pass a transform function that will be invoked after the remote call is done:

import { parse } from 'fast-xml-parser'

const trasformXmlToJson = (data: any) =>
  parse(data, { ignoreAttributes: false, attributeNamePrefix: '' })

myRemoteService.get('/rabbids', {}, {
  contentType: 'text/xml',
  responseType: 'text',
  transcodeResponse: trasformXmlToJson
})

All methods return a promise with parsed content (content type is JSON) or whatever transcodeResponse custom function returns.

In case of error during remote call it will be rertuned a rejected promise with interference instance