Bundler Reactor

5.0.3 · abandoned · verified Sun Apr 19

Bundler Reactor is a command-line interface (CLI) tool designed to quickly scaffold React single-page applications (SPAs). It provides an opinionated boilerplate setup leveraging `pakit` for asset bundling (handling ES6, JSX, CSS, JSON, code splitting, and livereload), `3dub` as a development server with browser history API fallback, and pre-configured integrations for Babel and ESLint. The tool simplifies initial project setup by generating a project structure and `npm` scripts for common tasks like starting a development server (`npm run start`) and creating production builds (`npm run build`). Currently at version 5.0.3, the project appears to have an infrequent release cadence, with the last update over 1.5 years ago, which may lead to out-of-date dependencies or configurations for a rapidly evolving React ecosystem.

Common errors

```
bundler-reactor: command not found
```
cause The `bundler-reactor` CLI tool was not installed globally or is not in your system's PATH.

fix Ensure the package is installed globally using `npm install -g bundler-reactor` and that your npm global bin directory is included in your system's PATH.
```
npm ERR! Missing script: start
```
cause The `start` script, or another npm script like `build`, is not defined in the `package.json` of your generated project, or you are running the command from the wrong directory.

fix Ensure you are in the root directory of your `bundler-reactor` generated project (e.g., `cd my-react-app`) and verify that `"scripts": { "start": "...", "build": "..." }` exist in your `package.json` file.
```
Error: Cannot find module 'react' or other project-level dependency errors
```
cause Dependencies for the newly generated `bundler-reactor` project have not been installed, or an installation failed.

fix Navigate into your generated project directory (e.g., `cd my-react-app`) and run `npm install` to install all project-specific dependencies.
```
Error: Cannot find module '@babel/core' or similar Babel-related build errors
```
cause The Babel setup within the generated project is outdated or misconfigured, often due to the project's lack of updates reflecting modern Babel versions and configurations, or an incomplete `npm install`.

fix Carefully review the `.babelrc` or `babel.config.js` file in your project. Ensure all Babel dependencies are correctly listed and installed. Consider manually upgrading Babel packages and adjusting the configuration to match the latest Babel documentation, especially if using a newer Node.js version.

Warnings

breaking The `bundler-reactor` project appears to be unmaintained. The last commit and release were over 1.5 years ago. This means generated projects may rely on outdated versions of React, Babel, ESLint, and other ecosystem dependencies, potentially leading to security vulnerabilities, compatibility issues with newer Node.js versions, or missing modern features.
Fix: Consider using more actively maintained React project scaffolding tools (e.g., Vite, Create React App, Next.js) or carefully audit and manually upgrade all generated project dependencies.
gotcha The `update` command, used to migrate `bundler-reactor` configurations, carefully avoids overriding modified files in your project. If conflicts occur, the migration will not complete, requiring manual intervention. Files in the `src` folder are never updated if modified.
Fix: To resolve conflicts, manually update the conflicting files. For files no longer requiring updates, set `detached: true` in their corresponding entries within `.bundler/.install` in your project root.
gotcha Configuration for core tools like Pakit, Babel, ESLint, and 3dub are managed through specific JSON files (e.g., `.pakit.json`, `.babelrc`, `.eslintrc.json`, `.3dub.json`). Misconfigurations in these files can lead to build failures, incorrect linting, or server issues.
Fix: Refer to the documentation for each respective tool (pakit, babel, eslint, 3dub) for correct configuration syntax and options. The `bundler-reactor` template provides sensible defaults that can be customized.

Install

npm install bundler-reactor npm
yarn add bundler-reactor yarn
pnpm add bundler-reactor pnpm

Imports

CLI Usage (Scaffold)
wrong:
```
import { create } from 'bundler-reactor'; create('my-new-app');
```
correct:
```
bundler-reactor my-new-app
```
This package is primarily a CLI tool and does not export programmatic JavaScript symbols for direct import. Its main function is to scaffold new projects via command line.
CLI Usage (Update)
wrong:
```
require('bundler-reactor').update();
```
correct:
```
bundler-reactor update
```
The 'update' command is executed via the CLI from within an existing `bundler-reactor` project directory to apply configuration updates to the boilerplate.
CLI Installation
wrong:
```
import * as BundlerReactor from 'bundler-reactor';
```
correct:
```
npm install -g bundler-reactor
```
The `bundler-reactor` tool is installed globally to make the `bundler-reactor` command available in your terminal. It is not intended for programmatic import or use as a library within application code.

Quickstart

Demonstrates how to install the `bundler-reactor` CLI, generate a new React application, install its dependencies, and start the local development server.

npm install -g bundler-reactor

# Create a new React application boilerplate
bundler-reactor my-react-app

# Navigate into the new project directory
cd my-react-app

# Install project-specific dependencies (React, Babel, etc.)
npm install

# Start the development server and open in browser
npm run start
# Open your browser to http://localhost:3000 (or as configured by .3dub.json)

view raw JSON →