# Is parcel-bundler ESM-only? Can you require() it?

> parcel-bundler@1.12.5 is a CommonJS package. CommonJS — require() works on Node.js 22 and 24, fails on 18, 20 and 26.

Blazing fast, zero configuration web application bundler

Last verified Sep 9, 2026 against parcel-bundler@1.12.5.

parcel-bundler ships CommonJS only. require("parcel-bundler") works on Node.js 22 and 24 but fails on Node.js 18, 20 and 26 (Error). The package declares Node.js >= 6.0.0. import "parcel-bundler" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.

**Deprecated:** Parcel v1 is no longer maintained. Please migrate to v2, which is published under the 'parcel' package. See https://v2.parceljs.org/getting-started/migration for details.

## What to do

1. require("parcel-bundler") works on Node.js 22 and 24 but fails on Node.js 18, 20 and 26 (Error). The package declares Node.js >= 6.0.0.
2. From ES modules use the default import: import parcelBundler from "parcel-bundler"; then destructure. Named imports only work when Node.js can statically detect the exports.
3. TypeScript: npm install -D @types/parcel-bundler
4. This package is deprecated: Parcel v1 is no longer maintained. Please migrate to v2, which is published under the 'parcel' package. See https://v2.parceljs.org/getting-started/migration for details.

## Facts

- Latest: 1.12.5 (Mar 16, 2021)
- Module format: CommonJS
- Last CommonJS version: 1.12.5
- TypeScript types: @types/parcel-bundler
- Node engines: >= 6.0.0
- Weekly downloads: 35K
- License: MIT

## Runtime test results for parcel-bundler@1.12.5

Installed and executed on Sep 9, 2026 with require("parcel-bundler") from a CommonJS file and import "parcel-bundler" from an ES module.

| Runtime | require("parcel-bundler") | import "parcel-bundler" |
|---|---|---|
| Node.js 18 | fails (Error) | fails (Error) |
| Node.js 20 | fails (Error) | fails (Error) |
| Node.js 22 | works | works |
| Node.js 24 | works | works |
| Node.js 26 | fails (Error) | fails (Error) |
| Bun 1.4.0 | fails (Error) | fails (Error) |

## How to import parcel-bundler

ES modules:

```js
import parcelBundler from "parcel-bundler";
```

CommonJS:

```js
const parcelBundler = require("parcel-bundler");
```

## Module format by version

Derived from the type, main and exports fields of every stable release on npm (39 versions; the newest 39 shown).

| Versions | Format | First published |
|---|---|---|
| 1.0.0 – 1.12.5 | CommonJS | Dec 5, 2017 |

## Frequently asked

**Is parcel-bundler ESM-only?**

parcel-bundler@1.12.5 is a CommonJS package. parcel-bundler ships CommonJS only. require("parcel-bundler") works on Node.js 22 and 24 but fails on Node.js 18, 20 and 26 (Error). The package declares Node.js >= 6.0.0. import "parcel-bundler" also works because Node.js and Bun can import CommonJS from ES modules, but only the default export is guaranteed; named imports depend on Node's static analysis of the module.

**Can I import parcel-bundler with ES module syntax?**

Yes. import parcelBundler from "parcel-bundler" works in Node.js and Bun because they support importing CommonJS modules. Named imports work only when Node.js can statically detect the exports.

**Does parcel-bundler work in Bun?**

Importing parcel-bundler failed in Bun 1.4.0 on Sep 9, 2026: error: Could not locate the bindings file. Tried:

**Does parcel-bundler ship TypeScript types?**

Not bundled. Install the community types with "npm install -D @types/parcel-bundler".

## Links

- [parcel-bundler on npm](https://www.npmjs.com/package/parcel-bundler)
- [Source repository](https://github.com/parcel-bundler/parcel)
- [HTML version](https://canirequire.com/package/parcel-bundler/)
- [JSON version](https://canirequire.com/package/parcel-bundler.json)

---

For scripts and AI agents: any package is at https://canirequire.com/package/<name>/index.md (Markdown) or https://canirequire.com/package/<name>.json (JSON); the site index is https://canirequire.com/llms.txt. Fetch the URL directly; no search needed.