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

strive

v0.4.0

Published

Strive. Don't give up. Try a bunch of different approaches to get what you're looking for.

Downloads

10

Readme

strive 💪

Strive. Don't give up. Try a bunch of different approaches to get what you're looking for.

npm version Build Status npm

Strive is a tool that allows you to try different techniques to accomplish a task, minus the boilerplate. Let's see how.

Suppose you were building an app that fetches song lyrics from some online services. The songs aren't popular, so there's no guarantee any single site (say, genius.com) will have them. So you have a couple of options. Here's how you could do this with strive:

    const strategies = [
        function tryGeniusAPI() {
        // try calling genius.com API
        },

        function tryMusixMatchAPI() {
        },

        function tryLyricFindAPI() {
        },

        function tryLastFM() {
        },
    ];
const didWeGetTheLyrics = (result) => {
    // some function that checks the results for lyrics
    // and returns true or false
}

const strive = require("strive");
const { result, lastAttempt, success } = await strive({
    strategies,
    check: didWeGetTheLyrics,
});

Strive will run the first strategy, then check its result by passing it to the check function (didWeGetTheLyrics). If the check returns false, Strive will move on to the next strategy, and so forth. When one of the strategies gives a result that passes the check, Strive will exit, returning a Promise that resolves to this:

{
  result: <yourSongLyrics>, // whatever value the successful strategy returned,
  lastAttempt: "tryLyricFindAPI", // the name of the successful strategy
  success: true
}

If none of the strategies produces a passing result, the response from Strive will look like this:

{
  result: <emptyLyrics>, // whatever value the last strategy returned,
  lastAttempt: "tryLastFM", // the name of the last strategy in the list
  success: false
}

An easier way - Using values

There's an easier way we could do this. Let's assume these site's APIs work in the same manner; the only thing different is the URLs. We could replace these separate strategies with a single action and a list of the different values to try. The action is the actual work that's done (calling an API), the values are the parameters Strive uses for the action:

    const values = [
        ["api.genius.com"],
        // You can pass multiple parameters
        ["api.musixmatch.com", apiKeys.musixmatch],
        ["lyricfind.com/api", apiKeys.lyricFind],
        ["api.last.fm", apiKeys.lastFM, {other: "parameter"}],
    ];
const { result, lastAttempt, success } = await strive({
    values,
    action: (apiUrl, apiKey, extraParams) => { /* Make the API call */ },
    check: didWeGetTheLyrics,
});

Strive will call the action with each set of values (URL, API key, extra parameters) until it gets a result that passes the check. The response from Strive is similar to when using strategies, with one change: the lastAttempt is the array index of the last value tried.

Using mutations

There's a middle ground between multiple strategies and multiple values with one action: multiple mutations, one action. Like before, the action is the actual work that's done (calling an API). The mutations provide Strive with the parameters for the action. Mutations, however, allow you to dynamically generate these parameters.

    const mutations = [
        function useGeniusAPI() {
            if (song.isOld()) {
                return ["old-api.genius.com"];
            }
            return ["api.genius.com"];
        },

        function useMusixMatchAPI() {
            return ["api.musixmatch.com", apiKeys.musixmatch];
        },

        function useLyricFindAPI() {
            return ["lyricfind.com/api", apiKeys.lyricFind];
        },

        function useLastFM() {
            return ["api.last.fm", apiKeys.lastFM, {other: "parameter"}];
        },
    ];
const { result, lastAttempt, success } = await strive({
    mutations,
    action: (apiUrl, apiKey, extraParams) => { /* Make the API call */ },
    check: didWeGetTheLyrics,
});

Similar to when using values, each mutation only has to return an array containing the parameters for the action. The elements of the returned array will be used when calling the action.

In the response from Strive, lastAttempt will be the name of the successful mutation, or the last mutation if none was successful.

Important notes

Function names

It is not recommended to use anonymous functions with Strive. This is because Strive uses the function's name property for logging and reporting purposes (lastAttempt). Anonymous functions do not have this value set.

const tryAzLyrics = function () {};
const tryLyricsFind = () => {};
const strategies = [
    function tryGenius () {}, // 👍 This is good
    tryAzLyrics, // 👍 This is good
    tryLyricFind, // 👍 This is good
    function () {}, // ❌ Bad, anonymous function 
    () => {}, // ❌ Bad, anonymous function 
];

Async operations

Strive will always return a Promise containing the result as described above. Async functions or functions returning Promises are also supported as mutations, actions and strategies; strive will await them before continuing.

Other options

There's a few other options you can pass to the strive function:

race

Strive runs all strategies/actions sequentially by default. If you want to run all in parallel and return the first successful one, then pass in race: true.

Note that this only works when you have functions that return promises. Strive will fire all of them off and return the first successful one (that passes the check) using promise.any.

const { result, lastAttempt, success } = await strive({
    strategies,
    race: true,
    check: didWeGetTheLyrics,
});

You should use this if you have multiple asynchronous operations, and you want the first successful one, and you don't care which one it is.

ignoreErrors

By default, if any errors are thrown while performing your action or strategy, strive will ignore them and move on to the next action/strategy (or return undefined if it's the final one).

⚠ Note that this is only while executing the action or any of the strategies. If an error occurs while executing one of the mutations, strive will quit and throw that error back at you.

If you want strive to quit when it encounters an error in an action or strategy, pass in ignoreErrors: false.

⚠ Note that when race is true and ignoreErrors is false, all errors will be ignored. Only if the last strategy fails is its error thrown.

defaultValue

By default, when strive runs through all the techniques and all of them fail the check, strive will return the following :

{
  result: <resultFromTheLastAttempt>,
  lastAttempt: <nameOfTheLastAttempt>,
  success: false,
}

You can specify a different value for the result by supplying a defaultValue. (Note that the lastAttempt and success values will still be as shown above.)

Logging

Strive uses the debug package to log info about the strategy, mutation or value it's currently trying. The debug name is lib:strive. This means if you start your application with the environment variable DEBUG=lib:strive )or use a wildcard), you'll see log messages like this:

Trying value at 0: "api.genius.com"
Trying strategy tryGeniusAPI
Trying mutation useGeniusAPI