build-utils

library2.0.12jsnpmunverified

build-utils is a JavaScript library offering a collection of utility functions primarily designed for build scripts. It encapsulates common operations across file system manipulation (`fs`), process execution (`process`), configuration updates (`config`), object transformations (`object`), and command-line interface (`cli`) helpers. The current stable version is 2.0.12, but it was last published on npm approximately eight years ago (August 2018). Due to its age, it primarily uses the CommonJS module system and is not actively maintained, meaning there are no new features, bug fixes, or security updates. It serves as a straightforward, albeit outdated, toolkit for basic automation tasks, lacking the modern features or dual ESM/CJS support found in contemporary alternatives.

devops serialization

npm install build-utils

github ↗package ↗

INSTALL

IMPORT

SIG · BUILD-UTILS

build-utils

devopsjavascriptv2.0.12

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.

createDirectory

✓ const { createDirectory } = require('build-utils');

✗ import { createDirectory } from 'build-utils';

This package is CommonJS-only due to its last publish date in 2018. ESM import syntax will result in a runtime error.

spawn

✓ const { spawn } = require('build-utils').process;

✗ import { process } from 'build-utils'; const { spawn } = process;

Functions are often grouped under namespaces like `process`. Direct ESM imports are not supported.

deepAssign

✓ const { deepAssign } = require('build-utils').object;

✗ import deepAssign from 'build-utils/object';

Individual utilities are exposed via their category namespace (e.g., `object.deepAssign`). Referencing sub-paths or default imports will not work.

This quickstart demonstrates basic file system operations (create, write, delete) and process execution using `build-utils` in a CommonJS Node.js environment.

const { createDirectory, writeFile, deleteDirectory } = require('build-utils').fs; const { exec } = require('build-utils').process; const path = require('path'); async function runBuildProcess() { const tempDir = path.join(__dirname, 'temp-output'); const tempFile = path.join(tempDir, 'artifact.txt'); console.log(`Creating directory: ${tempDir}`); await createDirectory(tempDir); console.log('Directory created.'); console.log(`Writing file: ${tempFile}`); await writeFile(tempFile, 'This is a build artifact generated by build-utils.\nHello, World!'); console.log('File written.'); console.log('Executing a command: ls'); try { const { stdout, stderr } = await exec('ls -l ' + tempDir); console.log('Stdout:', stdout); if (stderr) console.error('Stderr:', stderr); } catch (error) { console.error('Error executing command:', error.message); } console.log(`Cleaning up directory: ${tempDir}`); await deleteDirectory(tempDir); console.log('Cleanup complete.'); } runBuildProcess().catch(console.error);

Debug

Known issues

breakingThe `build-utils` package was last published in August 2018. It is unmaintained, which means there will be no new features, bug fixes, or security updates. Users should consider migrating to actively maintained alternatives for critical projects.

fix

Evaluate actively maintained build utility libraries or implement functionalities using Node.js's native `fs`, `child_process`, and `path` modules.

affects: >=2.0.12

breakingThis package is exclusively designed for CommonJS (CJS) environments and does not support ECMAScript Modules (ESM) syntax. Attempting to use `import` statements will lead to runtime errors in Node.js ESM projects.

fix

Ensure your project is configured for CommonJS, or use `require()` statements within a CJS-compatible file. For ESM projects, consider modern dual-module libraries.

affects: >=2.0.12

gotchaCompatibility with newer Node.js versions is uncertain due to the package's age. It may rely on deprecated Node.js APIs or exhibit unexpected behavior with recent runtime changes, potentially leading to instability or subtle bugs.

fix

Test thoroughly on your target Node.js version. If issues arise, direct replacement with Node.js built-ins or newer libraries is recommended.

affects: >=2.0.12

gotchaThe globbing utilities (`copyGlob`, `deleteGlob`, `searchGlob`) might use an outdated or custom glob implementation. This could lead to different behavior compared to modern, widely adopted globbing libraries (e.g., `fast-glob`), affecting pattern matching and file resolution.

fix

Verify glob patterns rigorously, especially for complex scenarios. If discrepancies are found, consider using a dedicated and maintained globbing library in conjunction with this package or as a replacement.

affects: >=2.0.12

Errors

Common errors & fixes

ReferenceError: require is not defined in ES module scope

Attempting to use `require()` in an ECMAScript Module (ESM) context when `build-utils` is a CommonJS-only package.

fix

Change your file's extension to `.cjs` or ensure your `package.json` specifies `"type": "commonjs"`. Alternatively, use dynamic `import()` for CJS modules within ESM, but be aware of potential interoperability complexities.

TypeError: Cannot read properties of undefined (reading 'createDirectory')

This error typically occurs when trying to destructure a property from `undefined`. It implies that `require('build-utils')` did not return an object with a `fs` property, or `fs` did not have `createDirectory`, likely due to incorrect import path or module resolution issues.

fix

Ensure you are correctly accessing utilities under their respective namespaces (e.g., `require('build-utils').fs.createDirectory`). Verify the exact function name and nesting from the package's source or documentation.

Error: spawn ENOENT

The `exec` or `spawn` utility within `build-utils.process` could not find the specified command in the system's PATH. This is a common operating system error when trying to run an unrecognized executable.

fix

Check that the command you are trying to execute (`ls`, `git`, `npm`, etc.) is installed and accessible in the system's PATH environment variable. Provide the full path to the executable if it's not globally available.

Upgrade

Version history

2.0.12latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

13 hits · last 30 days

node

Amazon

OpenAI (training)

Resources

githubhttps://github.com/oricalvo/build-utils ↗

packagehttps://www.npmjs.com/package/build-utils ↗