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

@bongione/redux-fetch-apptoken

v0.1.2

Published

Redux middleware that wraps ES6 fetch calls with an app token header

Downloads

2

Readme

Redux fetch app token

Redux middleware that wraps fetch calls with a http header that bears and app token.

Useful for non-full fledged HTTP bearer token OAuth2 implementations, like for microservice architecture that have a central authorization microservice that grants temporary app tokens to other microservices.

Usage

npm install --save @bongione/redux-fetch-apptoken

When setting up your redux store

let {createStore, applyMiddleware} = require('redux')
import {fetchWithAppTokenMiddleware} from '@bongione/redux-fetch-apptoken'

const options = {
    tokenFetchRequest: (url, scopes) => { ... },
    tokenFetchUrl: '/auth/users/app_token',
    httpAppTokenHeader: 'SENECA-APP-TOKEN'
}

const store = createStore(testApp, applyMiddleware(
        fetchWithAppTokenMiddleware(options)
    ))

The options object attributes are:

  • tokenFetchRequest a function with signature (url = '', scope = []) to retrieve the app tokens once the user has been authenticated
  • tokenFetchUrl the url used to retrieve the tokens
  • httpAppTokenHeader The HTTP header name to use where the token is attached to.

The middleware expects the token provider to return a json object of the format

{
    token: 'TOKENSTRING',
    expires_is_s: 3600
}

When you would usually call a fetch statement from an action

import {fetchWithAppToken} from '@bongione/redux-fetch-apptoken'

function testPostFetchAction (fetch, dispatch) {
    fetch
        .then(response => response.json())
        .then(json => {
            dispatch(saveData(json))
        })
        .catch(err => {
            console.log(err)
        })
}


store.dispatch(fetchWithAppToken('test_url', {}, 'TEST', testPostFetchAction))

fetchWithAppToken (url, fetch_options, scope, action) takes the following parameters:

  • url url to fetch from
  • fetch_options options you would use for your fetch called, like method, credentials, body...
  • scope The scope of the API you are calling. We expect the backend to be served by multiple microservices
  • action the action to perform after the fetch. Action should be a function with the following signature:
action(fetchPromise, dispatch)

The middleware will queue fetch requests until a valid token has been retrieved from the backend.