ultrabundle

library1.0.2jsnpmunverified

UltraBundle is an efficient and aggressive JavaScript/TypeScript bundler built upon Rollup, designed for projects requiring optimized output with minimal configuration. Currently at version 1.0.2, it appears to be under active development, though a specific release cadence is not explicitly stated. Its key differentiators include first-class TypeScript support, a comprehensive suite of out-of-the-box optimizations, and a straightforward single JSON file (`bundles.json`) configuration approach. Unlike more complex bundlers, it aims to simplify the bundling process by abstracting away much of the underlying Rollup configuration, providing presets for development, watching, and production builds with optimizations. This tool is intended for bundling application code, not libraries.

devops

npm install ultrabundle

github ↗package ↗

INSTALL

IMPORT

SIG · ULTRABUNDLE

ultrabundle

devopsjavascriptv1.0.2

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.

ultrabundle CLI (Development)

✓ "dev": "ultrabundle"

✗ import { ultrabundle } from 'ultrabundle'

UltraBundle is a CLI tool and not imported into JavaScript/TypeScript files. Its primary usage is via `package.json` scripts.

ultrabundle CLI (Watch Mode)

✓ "watch": "ultrabundle --watch"

✗ require('ultrabundle').watch()

Commands are executed directly as npm scripts or via `npx` for watch mode, which enables file watching.

ultrabundle CLI (Production Optimize)

✓ "prod": "ultrabundle --optimize"

✗ ultrabundle.optimize({ ... })

For production builds, the `--optimize` flag triggers additional optimizations. The configuration is handled through `bundles.json`, not programmatic API.

Demonstrates the typical setup for UltraBundle, including `package.json` scripts and the required `bundles.json` configuration file, showing a basic TypeScript input and JavaScript output.

{ "name": "my-app", "version": "1.0.0", "description": "My UltraBundled application", "main": "dist/output.js", "scripts": { "dev": "ultrabundle", "watch": "ultrabundle --watch", "prod": "ultrabundle --optimize" }, "devDependencies": { "ultrabundle": "^1.0.0" } } // -- In bundles.json -- [ { "input": "src/index.ts", "output": "dist/output.js" } ] // -- In src/index.ts -- console.log("Hello from UltraBundle!"); // To run: // 1. npm install // 2. npm run dev (for development build) // 3. npm run watch (for continuous watching and rebuilding) // 4. npm run prod (for optimized production build)

ultrabundle --version

Debug

Known issues

breakingAs a relatively new project (v1.0.2), UltraBundle's configuration schema (`bundles.json`) or CLI options might undergo breaking changes in future major versions. Users should review release notes carefully when upgrading to new major versions.

fix

Always check the official documentation or release notes for schema updates when upgrading to a new major version. Consider pinning to a specific major version to avoid unexpected build failures.

affects: >=1.0.0

gotchaUltraBundle's 'aggressive' optimizations, powered by Rollup, may unexpectedly remove code or side effects that are crucial for certain libraries or frameworks. This is common with strict tree-shaking.

fix

If encountering unexpected runtime errors or missing functionality, examine the bundled output. Look for `sideEffects: false` in `package.json` of affected libraries or use `/* #__PURE__ */` annotations for functions with side effects. Consult Rollup documentation for advanced `treeshake` options if UltraBundle exposes them or if a custom Rollup config can be injected.

affects: >=1.0.0

gotchaUltraBundle relies on a `bundles.json` file in the project root. If this file is missing, malformed, or located elsewhere, the bundling process will fail or produce an empty output.

fix

Ensure `bundles.json` exists in the same directory as `package.json` and follows the specified JSON array format. Verify all `input` and `output` paths are correct and accessible.

affects: >=1.0.0

gotchaWhile UltraBundle ships with TypeScript support, misconfigured `tsconfig.json` or incompatible TypeScript versions can lead to compilation errors during bundling.

fix

Ensure your project's `tsconfig.json` is correctly set up for your project, especially `target` and `module` options. Update TypeScript to a compatible version with UltraBundle and Rollup's underlying TS transformer. Check UltraBundle's GitHub issues for reported TS compatibility problems.

affects: >=1.0.0

Errors

Common errors & fixes

Error: No bundles.json file found in the root directory.

The `bundles.json` configuration file is missing or not located in the project's root directory (where `package.json` resides).

fix

Create a `bundles.json` file in your project's root directory, ensuring it contains a valid JSON array of bundle configurations.

Error: Could not resolve 'path/to/module' from 'path/to/source.ts'

A module import path could not be resolved by the bundler, typically due to incorrect relative paths, missing `node_modules` installations, or incorrect `baseUrl`/`paths` configuration in `tsconfig.json`.

fix

Double-check import paths in your source code. Ensure all dependencies are correctly installed (`npm install`). Verify `tsconfig.json`'s `compilerOptions.paths` and `compilerOptions.baseUrl` are set up correctly if using path aliases.

TypeError: Cannot read properties of undefined (reading 'value') during build.

This generic error often indicates an issue within the Rollup configuration or a plugin, potentially caused by an invalid or unexpected input, or a problem with a specific optimization pass.

fix

Review your `bundles.json` configuration for any typos or invalid properties. Try a simpler configuration first to isolate the problem. Check for recent changes in UltraBundle or Rollup that might affect your setup. Temporarily disable `--optimize` to see if the issue is related to aggressive optimizations.

Upgrade

Version history

1.0.2latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

5 hits · last 30 days

node

OpenAI (training)

Resources

githubhttps://github.com/ConsoleTVs/UltraBundle ↗

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