canirequire

canirequire › ESM-only › globby

Is globby ESM-only? Can you require() it?

User-friendly glob matching

Last verified Sep 9, 2026 against globby@16.2.4. Markdown · JSON

ESM-only ESM-only since 12.0.0 — last CommonJS version is 11.1.0

globby dropped its CommonJS build in 12.0.0 (July 2021). The last version with a plain require()-able CommonJS entry is 11.1.0, published Jan 8, 2022; it declares support for Node.js >=10.

On Node.js 20.19+, 22.12+ and newer, require("globby") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 20, 22, 24 and 26. Node.js 18 has no require(esm), and globby@16.2.4 declares Node.js >=20, so 18 is outside its supported range anyway.

globby@16.2.4 declares engines ">=20", so Node.js 18 is outside its supported range regardless of module format.

What to do

  1. On Node.js 20.19+, 22.12+ and newer, require("globby") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 20, 22, 24 and 26.
  2. From a CommonJS file, use a dynamic import inside an async function: const globby = await import("globby"). That works on every Node.js version the package supports (>=20).
  3. If you need a synchronous require() or run Node.js 18: npm install globby@11.1.0, the last CommonJS release (published Jan 8, 2022); it declares Node.js >=10.
  4. globby@16.2.4 declares engines ">=20", so Node.js 18 is unsupported regardless: upgrade Node.js or pin an older release.
  5. TypeScript: types are bundled; install nothing extra.
Latest
16.2.4 (Aug 19, 2026)
Module format
ESM-only
Last CommonJS version
11.1.0
ESM-only since
12.0.0 (Jul 22, 2021)
TypeScript types
Bundled
Node engines
>=20
Weekly downloads
83.1M
License
MIT

Does globby@16.2.4 actually load? Runtime test results

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

Runtimerequire("globby")import "globby"
Node.js 18✗ failsERR_REQUIRE_ESM✓ works
Node.js 20✓ works✓ works
Node.js 22✓ works✓ works
Node.js 24✓ works✓ works
Node.js 26✓ works✓ works
Bun 1.4.0✓ works✓ works

How to import globby

ES modules (import)

import * as globby from "globby";

Namespace import shown because the ESM entry may have no default export; use named imports for what it exports.

CommonJS (require)

// Node.js 20.19+, 22.12+ and newer (verified):
const globby = require("globby");

// Any Node.js version the package supports (>=20), from an async function:
async function main() {
  const globby = await import("globby");
}

// Or pin the last CommonJS release (declares Node.js >=10):
// npm install globby@11.1.0

Module format by version

Derived from the type, main and exports fields of every stable release on npm, corrected where a runtime test of that version contradicted them (59 versions; the newest 59 shown).

VersionsFormatFirst published
12.0.0 – 16.2.4ESM-onlyJul 22, 2021
0.1.0 – 11.1.0CommonJSJun 21, 2014

Frequently asked

Is globby ESM-only?

globby@16.2.4 is ESM-only. globby dropped its CommonJS build in 12.0.0 (July 2021). The last version with a plain require()-able CommonJS entry is 11.1.0, published Jan 8, 2022; it declares support for Node.js >=10.

Which version of globby still supports CommonJS / require()?

11.1.0 is the last version of globby with a CommonJS build; it declares Node.js >=10. Install it with "npm install globby@11.1.0". Every version from 12.0.0 on is ESM-only.

How do I use globby from a CommonJS file?

From a CommonJS file, use a dynamic import inside an async function: const globby = await import("globby"). That works on every Node.js version the package supports (>=20). On Node.js 20.19+, 22.12+ and newer, require("globby") works with the latest version: Node.js loads synchronous ES modules through require(). Verified on Node.js 20, 22, 24 and 26. Alternatively pin globby@11.1.0 (declares Node.js >=10).

Does globby work in Bun?

Yes. import "globby" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

Does globby ship TypeScript types?

Yes. globby bundles its own type declarations; no @types package is needed.

Links

Other esm-only packages

Similar popularity