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 🙏

© 2026 – Pkg Stats / Ryan Hefner

bashlink

v1.0.277

Published

Testable, predictable and scoped code in bash.

Readme

Project status

npm npm downloads

build push package

lint test

deploy documentation website documentation website

Use case

A bash framework to fill the gaps to write testable, predictable and scoped code in bash highly inspired by jandob's great tool rebash rebash.

Integrate bashlink into your bash script (only main entry file):

if [ -f "$(dirname "${BASH_SOURCE[0]}")/node_modules/bashlink/module.sh" ]; then
    # shellcheck disable=SC1090
    source "$(dirname "${BASH_SOURCE[0]}")/node_modules/bashlink/module.sh"
elif [ -f "/usr/lib/bashlink/module.sh" ]; then
    # shellcheck disable=SC1091
    source "/usr/lib/bashlink/module.sh"
else
    echo Needed bashlink library not found 1>&2
    exit 1
fi
bl.module.import bashlink.logging
# Your code comes here.

Integrate bashlink into your standalone bash script:

declare -gr MODULE_NAME_BASHLINK_PATH="$(
    mktemp --directory --suffix -module-name-bashlink
)/bashlink/"
mkdir "$MODULE_NAME_BASHLINK_PATH"
if curl \
    https://raw.githubusercontent.com/thaibault/bashlink/main/module.sh \
        >"${MODULE_NAME_BASHLINK_PATH}module.sh"
then
    declare -gr BL_MODULE_RETRIEVE_REMOTE_MODULES=true
    # shellcheck disable=SC1091
    source "${MODULE_NAME_BASHLINK_PATH}module.sh"
else
    echo Needed bashlink library not found 1>&2
    rm --force --recursive "$MODULE_NAME_BASHLINK_PATH"
    exit 1
fi
# Your standalone code comes here

Or combine both to implement a very agnostic script.

if [ -f "$(dirname "${BASH_SOURCE[0]}")/node_modules/bashlink/module.sh" ]; then
    # shellcheck disable=SC1090
    source "$(dirname "${BASH_SOURCE[0]}")/node_modules/bashlink/module.sh"
elif [ -f "/usr/lib/bashlink/module.sh" ]; then
    # shellcheck disable=SC1091
    source "/usr/lib/bashlink/module.sh"
else
    declare -gr MODULE_NAME_BASHLINK_PATH="$(
        mktemp --directory --suffix -module-name-bashlink
    )/bashlink/"
    mkdir "$MODULE_NAME_BASHLINK_PATH"
    if curl \
        https://raw.githubusercontent.com/thaibault/bashlink/main/module.sh \
            >"${MODULE_NAME_BASHLINK_PATH}module.sh"
    then
        declare -gr BL_MODULE_RETRIEVE_REMOTE_MODULES=true
        # shellcheck disable=SC1090
        source "${MODULE_NAME_BASHLINK_PATH}/module.sh"
    else
        echo Needed bashlink library not found 1>&2
        rm --force --recursive "$MODULE_NAME_BASHLINK_PATH"
        exit 1
    fi
fi
# Your portable code comes here.

Best practise (entry) module pattern:

if [ -f "$(dirname "${BASH_SOURCE[0]}")/node_modules/bashlink/module.sh" ]; then
    # shellcheck disable=SC1090
    source "$(dirname "${BASH_SOURCE[0]}")/node_modules/bashlink/module.sh"
elif [ -f "/usr/lib/bashlink/module.sh" ]; then
    # shellcheck disable=SC1091
    source "/usr/lib/bashlink/module.sh"
else
    declare -gr MODULE_NAME_BASHLINK_PATH="$(
        mktemp --directory --suffix -module-name-bashlink
    )/bashlink/"
    mkdir "$MODULE_NAME_BASHLINK_PATH"
    if curl \
        https://raw.githubusercontent.com/thaibault/bashlink/main/module.sh \
            >"${MODULE_NAME_BASHLINK_PATH}module.sh"
    then
        declare -gr BL_MODULE_RETRIEVE_REMOTE_MODULES=true
        # shellcheck disable=SC1090
        source "${MODULE_NAME_BASHLINK_PATH}/module.sh"
    else
        echo Needed bashlink library not found 1>&2
        rm --force --recursive "$MODULE_NAME_BASHLINK_PATH"
        exit 1
    fi
fi
bl.module.import bashlink.exception
bl.module.import bashlink.logging
bl.module.import bashlink.tools
alias moduleName.main=moduleName_main
moduleName_main() {
    bl.exception.activate
    # Your entry code.
    bl.exception.deactivate
}
# Your module functions comes here.
if bl.tools.is_main; then
    moduleName.main "$@"
    [ -d "$MODULE_NAME_BASHLINK_PATH" ] && \
        rm --recursive "$MODULE_NAME_BASHLINK_PATH"
    # shellcheck disable=SC2154
    [ -d "$BL_MODULE_REMOTE_MODULE_CACHE_PATH" ] && \
        rm --recursive "$BL_MODULE_REMOTE_MODULE_CACHE_PATH"
fi