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

overridable-fn

v2.1.3

Published

Simple utility to define functions whose behavior can be overriden at runtime

Downloads

41

Readme

overridable-fn

Create functions whose behavior can be swapped out dynamically.

Intended to be a lightweight less-intrusive alternative to IoC containers.

Let's say you have this function:

const getUserById = async (id: string) => {
    // ... fetch users from database
}

Now if you just wrap this function with fn:

import { fn } from "overridable-fn"

const getUserById = fn(async (id: string) => {
    // ... fetch users from database
})

The behavior of getUserById remains unchanged

getUserById(10) //-> fetches users from database

However, you can now override the implementation (eg. in tests)

getUserById.override((prevImpl) => async (id: string) => {
    console.log('[WARN] Returning fake user')
    return new User({ id })
})

So if you call getUserById() now, your overriden implementation be invoked instead.

Note: fn returns a wrapped function - it does not modify the function passed to it. So after wrapping you must always invoke the wrapper returned by fn.

const getUserByIdImpl = async (id: string) => { /* Get user from database */ }
const getUserById = fn(getUserByIdImpl) // getUserById is a wrapper which invokes getUserByIdImpl
getUserById.override(() => async (id: string) => { /* Return fake user */ })
getUserById() // Returns fake user
getUserByIdImpl() // Returns user from database, because wrapper is not used

You can access the wrapped function by using unwrap. Calling unwrap does not change the wrapper anyhow.

const getUserByIdImpl = async (id: string) => { /* Get user from database */ }
const getUserById = fn(getUserByIdImpl) // getUserById is a wrapper which invokes getUserByIdImpl
getUserById.unwrap() === getUserByIdImpl // true
getUserById.override(() => async (id: string) => { /* Return fake user */ })
getUserById.unwrap() === getUserByIdImpl // false
$ getUserById(10)
[WARN] Returning fake user

The handle returned from override has a restore function that can be used to restore the previous implementation.

describe('Your feature', () => {
    let restore;

    before(() => {
        ({ restore } = getUserById.override((prevImpl) => async () => {
            // ... mock implementation
        }))
    })

    after(() => {
        restore?.()
    })

    test("use overriden impl", async () => {
        const fakeUser = await getUserById(10)
    })
})

Please note that the handle returned from the override is able to restore only to the implementation before the override.

const wrapper = fn(() => 1)
wrapper.override(() => () => 2)
const { restore } = wrapper.override(() => () => 3)
restore()
wrapper() // 2
restore() // Repeated calls to restore have no further effect
wrapper() // 2