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

byu-wso2-request

v3.3.3

Published

Utility for making a server to server request using wso2 authentication

Downloads

801

Readme

BYU logo byu-wso2-request

Utility for making a server to server request using wso2 authentication

codecov

Requires Node 10+

Installation

npm i --save byu-wso2-request

Migration from v1 to v2.1+

  • Update to Node 8 or above
  • Use promises instead of callbacks for request

Migration from v2 to v3

  • Update to Node 10 or above
  • If you want the statusCode property added to responses, make the requests with the resolveWithFullResponse option set to true (See: #30)

Usage

Set up with setOauthSettings and then make requests with request

Examples:

const wso2 = require('byu-wso2-request')

(async () => {
  // Will default to api.byu.edu if host is not passed in
  const production = process.env.ENVIRONMENT_NAME === 'prd'
  const host = production ? 'api.byu.edu' : 'api-sandbox.byu.edu'
  
  // Alternatively, you can set the host in the environment variables
  // process.env.WSO2_HOST = 'api.byu.edu'

  // Do this once on startup
  await wso2.setOauthSettings('myClientKey', 'myClientSecret', { host })
  
  // After that, make all the requests you want
  try {
    // Simple GET request
    const response1 = await wso2.request({ url: `https://${host}/echo/v1/echo/test` })

    // Request using another method
    const response2 = await wso2.request({ method: 'PUT', url: `https://${host}/byuapi/students/v2/123456789/enrolled_classes/Summer2019,BIO,100,001`, body: { credit_hours: 3 } })
    
    // Request that passes along an original JWT
    const response3 = await wso2.request({ url: `https://${host}/echo/v1/echo/test` }, 'some original jwt to pass along')
    
    // Request where you want to know what status code came back (instead of just rejecting if it's not 2XX)
    const response4 = await wso2.request({ url: `https://${host}/echo/v1/echo/test`, simple: false, resolveWithFullResponse: true })
  } catch (e) {
    console.error(e) // Handle errors
  }
})

For more information on the options you can use for the request function, see request-promise