zero-bundler

library0.0.16jsnpmunverified

Zero Bundler, also known as `libpacker` on GitHub, is a command-line interface (CLI) tool designed for bundling npm packages with minimal configuration. It aims to simplify the build process for libraries by leveraging convention over explicit configuration, similar to other 'zero-config' bundlers like Microbundle or Parcel (v1). The tool processes entry files specified in `package.json` and generates output in both CommonJS (`main`) and ES Module (`modules`) formats. The latest available version is 0.0.16, published approximately four years ago. Due to its last update dating back to 2021 and its very low version number, the project appears to be unmaintained or abandoned, which impacts its compatibility with modern JavaScript and Node.js ecosystems, as well as the adoption of newer bundling optimizations.

devops

npm install zero-bundler

github ↗package ↗

INSTALL

IMPORT

SIG · ZERO-BUNDLER

zero-bundler

devopsjavascriptv0.0.16

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

zero

✓ This package is primarily a CLI tool and is executed via a `package.json` script, e.g., `"build": "zero"`. There are no direct JavaScript/TypeScript symbols intended for `import` or `require`.

Zero Bundler exposes a `zero` command-line executable after installation, not a library for programmatic import. Its functionality is accessed solely through the terminal.

Demonstrates how to configure `package.json` and a simple source file to build a library using the `zero` command.

{ "name": "my-awesome-lib", "version": "1.0.0", "description": "A simple library bundled with Zero Bundler.", "source": "./src/index.js", "main": "dist/index.js", "module": "dist/index.mjs", "scripts": { "build": "zero", "prepublishOnly": "yarn build" }, "devDependencies": { "zero-bundler": "^0.0.16" } } // In src/index.js export const greet = (name) => `Hello, ${name}!`; export const add = (a, b) => a + b; // To run: // 1. yarn add zero-bundler --dev // 2. yarn build // This will generate dist/index.js (CJS) and dist/index.mjs (ESM)

zero-bundler --version

Debug

Known issues

breakingThe `zero-bundler` project (GitHub: `libpacker`) appears to be abandoned, with its last commit over four years ago and no significant updates since version 0.0.16. This means it is unlikely to receive bug fixes, security patches, or updates for compatibility with newer Node.js versions, JavaScript language features, or evolving module resolution standards (`"exports"` field).

fix

Consider migrating to actively maintained zero-config bundlers like `bunchee`, `microbundle`, or `Parcel` for better support, modern features, and ongoing compatibility.

affects: >=0.0.16

gotchaAs an unmaintained bundler, `zero-bundler` may not support modern TypeScript features, JSX transforms, or advanced bundling optimizations like Rust-based compilers, tree-shaking across complex module graphs, or CSS/asset handling, which are common in contemporary build tools.

fix

Evaluate your project's needs carefully. For TypeScript or more complex web projects, an actively developed bundler will offer superior support and performance. If simple CJS/ESM bundling is all that's required, ensure thorough testing against your target environments.

affects: >=0.0.1

gotchaThe documentation is minimal, and due to its abandonment, community support is non-existent. Debugging issues related to module resolution, dependency handling, or specific bundling behaviors will be challenging without active development or community forums.

fix

For new projects, prioritize tools with comprehensive documentation and an active community. For existing projects, consider moving away from `zero-bundler` to mitigate future maintenance risks.

affects: >=0.0.1

Errors

Common errors & fixes

Error: Command 'zero' not found

The `zero-bundler` package was not installed or installed incorrectly, or the `zero` executable is not in the system's PATH.

fix

Ensure `zero-bundler` is installed as a development dependency (`yarn add zero-bundler --dev` or `npm install zero-bundler --save-dev`). If running directly, ensure `node_modules/.bin` is in your PATH, or execute via `yarn zero` or `npm run zero` if defined in scripts.

Error: Cannot find module '...' or 'Could not resolve '...' from ...'

The bundler failed to resolve an imported module, possibly due to incorrect paths, missing dependencies, or incompatibility with Node.js's evolving module resolution algorithms (e.g., `exports` field).

fix

Verify that all imported dependencies are correctly installed and listed in `package.json`. If using advanced module features like path aliases, `zero-bundler` may not support them. Manually ensure all paths are relative or standard npm package names.

Upgrade

Version history

0.0.16latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

20 hits · last 30 days

node

Resources

githubhttps://github.com/beizhedenglong/libpacker ↗

packagehttps://www.npmjs.com/package/zero-bundler ↗