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

@justjurt/bcc

v1.2.1

Published

Simple bundler+minifier for Computer Craft Lua projects

Readme

BCC

BCC is a command-line bundler and minifier for ComputerCraft Lua projects. It collects a project's Lua files into one runnable file, rewrites require so bundled modules are loaded from that file, and optionally shortens identifiers and removes comments and whitespace.

Requirements

  • Node.js
  • A Lua project with a main.lua file at its project root

Install

Install the published CLI globally:

npm install --global @justjurt/bcc

Or, when working from a local clone, invoke main.js with Node. Run BCC from the Lua project directory, because input files and output paths are relative to the current working directory.

cd path/to/my-lua-project
bcc

For example, from this repository's sample project:

cd _testing
node ../main.js

What compilation does

  1. Finds project files whose paths contain .lua, excluding paths with a build directory and patterns ignored by .bccignore.
  2. Wraps each included file in a function and bundles them into build/app.lua.
  3. Runs app.main(args), so the project's root main.lua is the entry point.
  4. Minifies build/app.lua in place unless minification is disabled.

For a one-level directory path such as data/data.lua, the bundle exposes the module as require('data.data'). Keep modules at the project root or one directory level deep; deeper paths are not reliably converted to module names by the current bundler.

Command-line arguments

| Argument | Description | | --- | --- | | -nm, --no-minify | Bundle the project without minifying the output. | | -w, --watch | Compile once, then watch the current project directory and recompile after detected changes. | | --ignore [pattern ...] | Create .bccignore if needed and append the given patterns. If no patterns are supplied, only create the file. This operation exits without compiling. |

Examples:

bcc --no-minify
bcc -w
bcc --ignore examples/ temp.lua
bcc --ignore

.bccignore uses gitignore-style patterns, with paths relative to the project directory. It is read during each bundle. Patterns supplied to --ignore are appended only if they are not already present; use --ignore without patterns to create the file, then edit it to remove or change entries.

Watch mode relies on Node.js recursive filesystem watching, which may vary by operating system and filesystem. The generated build output is excluded from bundling.

Output

The compiled program is written to build/app.lua. The output directory is created automatically. If minification is enabled, the same file is replaced with its minified version.

Development

The package exposes bcc through main.js. The bundler/bundle.js and minify/minify.js modules can also be run directly with Node or required as functions. There is currently no automated test suite configured in package.json.