{"id":15946,"library":"zero-bundler","title":"Zero Bundler (libpacker)","description":"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.","status":"abandoned","version":"0.0.16","language":"javascript","source_language":"en","source_url":"https://github.com/beizhedenglong/libpacker","tags":["javascript"],"install":[{"cmd":"npm install zero-bundler","lang":"bash","label":"npm"},{"cmd":"yarn add zero-bundler","lang":"bash","label":"yarn"},{"cmd":"pnpm add zero-bundler","lang":"bash","label":"pnpm"}],"dependencies":[],"imports":[{"note":"Zero Bundler exposes a `zero` command-line executable after installation, not a library for programmatic import. Its functionality is accessed solely through the terminal.","symbol":"zero","correct":"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`."}],"quickstart":{"code":"{\n  \"name\": \"my-awesome-lib\",\n  \"version\": \"1.0.0\",\n  \"description\": \"A simple library bundled with Zero Bundler.\",\n  \"source\": \"./src/index.js\",\n  \"main\": \"dist/index.js\",\n  \"module\": \"dist/index.mjs\",\n  \"scripts\": {\n    \"build\": \"zero\",\n    \"prepublishOnly\": \"yarn build\"\n  },\n  \"devDependencies\": {\n    \"zero-bundler\": \"^0.0.16\"\n  }\n}\n// In src/index.js\nexport const greet = (name) => `Hello, ${name}!`;\nexport const add = (a, b) => a + b;\n\n// To run:\n// 1. yarn add zero-bundler --dev\n// 2. yarn build\n// This will generate dist/index.js (CJS) and dist/index.mjs (ESM)","lang":"javascript","description":"Demonstrates how to configure `package.json` and a simple source file to build a library using the `zero` command."},"warnings":[{"fix":"Consider migrating to actively maintained zero-config bundlers like `bunchee`, `microbundle`, or `Parcel` for better support, modern features, and ongoing compatibility.","message":"The `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).","severity":"breaking","affected_versions":">=0.0.16"},{"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.","message":"As 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.","severity":"gotcha","affected_versions":">=0.0.1"},{"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.","message":"The 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.","severity":"gotcha","affected_versions":">=0.0.1"}],"env_vars":null,"last_verified":"2026-04-21T00:00:00.000Z","next_check":"2026-07-20T00:00:00.000Z","problems":[{"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.","cause":"The `zero-bundler` package was not installed or installed incorrectly, or the `zero` executable is not in the system's PATH.","error":"Error: Command 'zero' not found"},{"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.","cause":"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).","error":"Error: Cannot find module '...' or 'Could not resolve '...' from ...'"}],"ecosystem":"npm"}