Registry / devops / fusebox-cli

fusebox-cli

JSON →
library1.3.135jsnpmunverified

FuseBox is a JavaScript bundler and module loader known for its fast bundling times and zero-configuration approach for common setups. It aims to combine features found in tools like webpack and SystemJS. Key differentiators include first-class TypeScript support, built-in Rollup integration, and a developer-friendly experience with a fast dev server and Hot Module Replacement (HMR). The latest major version of the core bundler, `fuse-box`, is v4.0.0, released in April 2020. However, development appears to have ceased, with no significant updates to the core library since then, and the `fusebox-cli` package itself has not been updated since February 2018. Users should be aware that the project is effectively abandoned, lacking active maintenance or a release cadence, making it a potentially risky choice for new or ongoing projects requiring support and modern compatibility.

npm install fusebox-cli
INSTALL
IMPORT
SIG · FUSEBOX-CLI
F
fusebox-cli
devopsjavascriptv1.3.135
Install
Import
Disk
Pass rate
0/ 6
Env Coverage0 / 6
glibc
1822
musl
1822
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 18226 runs
build_error
glibc
node 18226 runs
build_error
Code
Verified usage

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

FuseBox
import { FuseBox } from 'fuse-box';
import FuseBox from 'fuse-box';
This is the primary class for configuring and running the bundler. Requires the `fuse-box` package, not `fusebox-cli`. Assume named import for TypeScript environments.
FuseBox
const { FuseBox } = require('fuse-box');
const FuseBox = require('fuse-box');
For CommonJS environments. While FuseBox supports modern targets, many build scripts might still use CommonJS `require` syntax. Destructuring is typical for named exports.

This example demonstrates how to initialize FuseBox with basic configuration for a TypeScript project and bundle a single entry file into an output file.

import { FuseBox } from 'fuse-box'; // Basic configuration for bundling a TypeScript project const fuse = FuseBox.init({ homeDir: "src/", sourceMap: { bundleReference: "./sourcemaps.js.map", outFile: "sourcemaps.js.map" }, outFile: "./out.js", cache: true, log: true }); // Bundle the main entry point 'index.ts' fuse.bundle(">index.ts"); // To run the development server with HMR (Hot Module Replacement) // fuse.dev({ // port: 4444, // hmr: true, // }); // fuse.bundle(">index.ts");
fusebox --version
Debug
Known issues
breakingVersion 4.0.0 of the `fuse-box` core library introduced significant changes and improvements, which are likely to include breaking changes from previous major versions (v3.x). Directly upgrading without consulting the documentation can lead to build failures.
fix
Consult the official FuseBox v4 documentation (fuse-box.org/docs/getting-started/setup) for migration details and updated configuration options. Review your `fuse.js` or configuration file for compatibility.
affects: >=4.0.0
breakingThe `fuse-box` bundler project and its companion `fusebox-cli` appear to be abandoned. The core `fuse-box` library has not seen updates since April 2020 (v4.0.0), and `fusebox-cli` has not been updated since February 2018 (v1.3.135). Continued use may lead to compatibility issues with newer Node.js versions, security vulnerabilities, or lack of support for modern JavaScript/TypeScript features.
fix
Consider migrating to an actively maintained bundler (e.g., Webpack, Rollup, Vite, esbuild) for new projects or existing projects requiring ongoing support, security updates, and compatibility with the latest ecosystem standards.
affects: >=1.0.0 (fusebox-cli), >=4.0.0 (fuse-box)
gotchaThere is a distinction between the `fusebox-cli` package and the `fuse-box` core library. While `fusebox-cli` provides command-line utilities, the main bundler logic and its configuration are handled by the `fuse-box` package. It's crucial to install `fuse-box` as the core dependency, not just `fusebox-cli`, for bundler functionality.
fix
Always ensure the `fuse-box` package is installed as a development dependency: `npm install fuse-box --save-dev` or `yarn add fuse-box --dev`. The quickstart often recommends `npm install typescript fuse-box --save-dev`.
affects: *
Errors
Common errors & fixes
TypeError: FuseBox.init is not a function
The `fuse-box` package was not imported correctly, or the `fusebox-cli` package was installed instead of the core `fuse-box` library which contains the `FuseBox` class.
fix
Ensure `fuse-box` is installed (`npm install fuse-box --save-dev`) and imported using `import { FuseBox } from 'fuse-box';` for ESM or `const { FuseBox } = require('fuse-box');` for CommonJS.
TS2307: Cannot find module 'fuse-box' or its corresponding type declarations.
The `fuse-box` package is not installed in your project's `node_modules`, or TypeScript cannot resolve its type definitions.
fix
Install `fuse-box` as a development dependency: `npm install fuse-box --save-dev` or `yarn add fuse-box --dev`. If using TypeScript, ensure your `tsconfig.json` is correctly configured to include `node_modules/@types`.
SyntaxError: Cannot use import statement outside a module
You are attempting to use ECMAScript Modules (ESM) `import` syntax in a file or environment configured for CommonJS (CJS).
fix
Either configure your project to use ESM (e.g., add `"type": "module"` to `package.json`, or use a `.mjs` file extension for your build script) or switch to CommonJS `require` syntax: `const { FuseBox } = require('fuse-box');`.
Upgrade
Version history
1.3.135latest on npm
Audit
Dependencies
typescriptoptionalCrucial for development, especially when using FuseBox's first-class TypeScript support. Explicitly mentioned in the quickstart installation.
Agent activity
4 hits · last 30 days
node
4
Resources
fusebox-cli — npm install fusebox-cli · libregistry