builderz

library0.11.0jsnpmunverified

Builderz is a zero-configuration JavaScript and TypeScript bundler designed for simplicity and efficiency, aiming to streamline the build process for both libraries and applications by minimizing setup overhead. The current stable version is `0.11.0`, with a development cadence that sees frequent minor updates and patch releases, typically addressing dependency updates, performance enhancements like caching, and bug fixes. Key differentiators include its 'zero-configuration' approach, the ability to build packages even with invalid `package.json` files (addressing a common development pain point), support for parallel build tasks for improved performance, and a robust caching mechanism introduced in `v0.10.0`. It supports both CommonJS (CJS) and ES Module (ESM) output formats and offers both a Command Line Interface (CLI) and a programmatic API for integration into development workflows.

devops

npm install builderz

github ↗package ↗

INSTALL

IMPORT

SIG · BUILDERZ

builderz

devopsjavascriptv0.11.0

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.

build

✓ import { build } from 'builderz'

✗ const { build } = require('builderz')

Builderz primarily uses ESM for its programmatic API. While CommonJS `require` might work in some contexts, ESM imports are the recommended and most robust approach.

watch

✓ import { watch } from 'builderz'

✗ const { watch } = require('builderz')

Used for development mode to automatically rebuild on file changes. Follows the same ESM import recommendation as `build`.

defineConfig

✓ import { defineConfig } from 'builderz'

✗ import defineConfig from 'builderz'

This utility function is specifically for type-checking and autocompletion in your `builderz.config.js` or `builderz.config.ts` file, and is a named export.

Demonstrates setting up a `package.json`, a `builderz.config.js` with ES module support, and an entry file, then running a build via CLI.

{ "name": "my-builderz-app", "version": "1.0.0", "type": "module", "scripts": { "build": "builderz build -c builderz.config.js", "start": "node dist/esm/index.js" }, "devDependencies": { "builderz": "^0.11.0" } } // builderz.config.js import { defineConfig } from 'builderz'; export default defineConfig({ entries: ['src/index.js'], output: { dir: 'dist', formats: ['esm', 'cjs'], fileName: '[name].[format].js' }, plugins: [], external: [] // Example: externalize node built-in modules }); // src/index.js import path from 'node:path'; import url from 'node:url'; const __dirname = path.dirname(url.fileURLToPath(import.meta.url)); console.log(`Hello from Builderz! Running from: ${__dirname}`);

builderz --version

Debug

Known issues

breakingThe arguments for the `builderz` CLI and potentially its programmatic API were updated in `v0.9.0`. This might require changes to existing build scripts or configurations.

fix

Refer to the updated documentation on the GitHub repository for the correct argument structure and configuration options for `builderz.config.js` files.

affects: >=0.9.0

gotchaAs a 'zero-configuration' bundler, Builderz makes many assumptions by default. While this simplifies setup, it can be less flexible for highly customized build requirements or complex monorepos without explicit configuration overrides.

fix

For custom behaviors, utilize the `builderz.config.js` file and its `plugins` option. Inspect the generated output to understand default behaviors. Consider other bundlers if deep, fine-grained control is consistently required beyond what `builderz` exposes.

affects: >=0.1.0

gotchaStarting from `v0.10.0`, the internal caching mechanism was switched from using a `Map` to a plain JavaScript object. While this is primarily an internal change, it could theoretically have subtle performance implications or edge-case behaviors in very specific environments or with extremely large projects.

fix

Monitor build times and cache effectiveness after updating to `v0.10.x` or later. If unexpected performance degradation occurs, consider reverting or reporting an issue to the maintainers.

affects: >=0.10.0

Errors

Common errors & fixes

Error: Cannot find module 'builderz'

The 'builderz' package is not installed or incorrectly referenced in your project's `node_modules`.

fix

Run `npm install builderz` or `yarn add builderz` to add it to your project's dependencies. Ensure your `package.json` correctly lists it under `devDependencies` or `dependencies`.

Error: Invalid or missing configuration file

The `builderz` command was run without a specified configuration file, or the specified file (`-c`) could not be found or parsed.

fix

Ensure you have a `builderz.config.js` (or `.ts`) file in your project root, or explicitly point to its location using `builderz build -c ./path/to/builderz.config.js`. Verify the file's syntax for any JavaScript/TypeScript errors.

Build failed with errors

Generic error indicating an issue during the bundling process, often related to syntax errors in source code, missing dependencies, or incorrect plugin configuration.

fix

Examine the console output for more specific error messages, which will usually pinpoint the problematic file or configuration setting. Check your source code for syntax errors, ensure all imported modules exist, and verify your `builderz.config.js` is valid.

Upgrade

Version history

0.11.0latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

5 hits · last 30 days

node

Resources

githubhttps://github.com/jalal246/builderz ↗

packagehttps://www.npmjs.com/package/builderz ↗