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 🙏

© 2025 – Pkg Stats / Ryan Hefner

bordeaux

v1.0.5-1

Published

Revolutionize the Makefile.

Readme

Bordeaux

Stars LoC
Revolutionize the Makefile. View on NPM

Usage

positional arguments:
  operation             What operation are we running? ('build' or 'transpile')

optional arguments:
  -h, --help            show this help message and exit
  -v, --verbose         Show verbose information.
  -f FLAGS [FLAGS ...], --flags FLAGS [FLAGS ...]
                        Flags to pass to Make. (Only used with 'build')
  -t TARGET, --target TARGET
                        Target to build. (Only used with 'build')
  -o OUTFILE, --outfile OUTFILE
                        File to send result to. (Only used with 'transpile')
  -i INPUT, --input INPUT
                        Input JSON / YAML file. (Defaults to 'BordeauxFile')

Example

Let's say we wanted to make a project. We want this project to:

  • use gcc as a compiler
  • print Hello, world! when run
  • use Bordeaux as a compilation utility

We'd start by writing our program. We'd end up with a little something like:

#include <stdio.h>

int main() {
  printf("Hello, World!\n");
  return 0;
}

Then we can test it.

gcc -o project.o project.c
./project.o
> Hello, World!

Great, it works! The hard part is done; now we need to write our Bordeaux file. Let's call our build target proj. We'll write something like this to BordeauxFile:

path: /usr/bin
defaultTarget: proj
targets:
    proj:
        runner: gcc -o project.o project.c
        silent: true

In order to test our newly created build file, we just need to run brdx build.

brdx build
> WARNING: You didn't specify a target to build. We'll be building the provided default target (if any).
> INFO: Transpiled.
> INFO: Using default target. (proj)
> INFO: Building target 'proj'...
> INFO: Built.

That's it! Now, we have our project fully completed.