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

tcbuilder

v1.0.4

Published

Build System

Downloads

21

Readme

bb (Bash-based build system)

Generate a automated Makefile from bash variables

Prerequisites

  • Bash
  • Make (for running the generated)

Installation

You can either install to your operating system or install to your project

Installing to Project

  1. Add bb to your project

    git submodule add --depth 1 https://github.com/umtozkn/bb.git
  2. Installing to operating system

  3. Create a any build variables file

    Create a file with starting with;

    if you installed bb to your project:

    #! ./bb/bb

    if you installed bb to your operating system:

    #! /usr/bin/bb

    ./bb/bb and /usr/bin/bb refers to where bb located

  4. Running

    If you haven't setup the rest of build variables, please go to Configuration section

    Now run the file that you created and it will output Makefile

    To compile your project, run make

Configuration

You can see variables that bb recognizes, look build.vars file

Docs

The ... refers, a value that contains in group variable (keep reading)

  • all_silent: Defines whatever make command outputs be suppressed, true by default, set false to show outputs
  • all_final_flags: Defines flags of final output, not replaced by other variables
  • default_final_executable: Defines executable of final output, replaced by ..._final_executable if defined
  • var_default_final_flags: Defines flags of final output, replaced by ..._final_flags if defined
  • all_extension_(extension)_flags: Defines flags of every (extension) files, not replaced by other variables
  • default_extension_(extension)_executable: Defines executable of every (extension) files, replaced by ..._default_extension_(extension)_executable if defined
  • default_source_(name)_(extension)_executable: Defines executable of one file in every groups, replaced by ..._source_(name)_(extension)_executable if defined
  • default_source_(name)_(extension)_flags: Defines flags of one file in every groups, not replaced by other variables
  • groups: This variable is main criticial variable for generating makefile, can not contain all or default, can take multiple values (eg. groups="foo bar"), the ... refers one of values that group contains
  • ..._description: Description of target
  • ..._build_dir: Build path where the files will be emitted, never leave empty
  • ..._sources: Can take many values (eg. "foo bar") but values should be relative path instead of full path
  • ...all_extension(extension)_flags: Defines flags of every (extension) file in ... group, not replaced by other variables
  • ...default_extension(extension)_executable: Defines executable of every (extension) file in ... group, replaced by default_source_(name)_(extension)_executable if defined
  • ...source(name)_(extension)_executable: Defines executable of (name).(extension) file in ... group, not replaced by other variables
  • ..._final_executable: Defines executable of final output in ... group,, not replaced by other variables
  • ..._final_flags: Defines flags of final output in ... group, not replaced by other variables