canirequire

canirequire › ESM-only › env-paths

Is env-paths ESM-only? Can you require() it?

Get paths for storing things like data, config, cache, etc

Last verified Sep 9, 2026 against env-paths@4.0.0. JSON

ESM-only ESM-only since 3.0.0 — last CommonJS version is 2.2.1

env-paths dropped its CommonJS build in 3.0.0 (August 2021). The last version you can require() on every Node.js version, including 18 and older, is 2.2.1, published Mar 8, 2021.

On Node.js 20.19+, 22.12+ and every newer release, require("env-paths") works anyway: Node can load synchronous ES modules through require(). Verified on Node 20, 22, 24, 26. Node.js 18 and older still fail with ERR_REQUIRE_ESM.

env-paths@4.0.0 declares engines ">=20", so Node.js 18 is outside its supported range regardless of module format.

Latest
4.0.0 (Jan 24, 2026)
Module format
ESM-only
Last CommonJS version
2.2.1
ESM-only since
3.0.0 (Aug 27, 2021)
TypeScript types
Bundled
Node engines
>=20
Weekly downloads
77.6M
License
MIT

Does env-paths@4.0.0 actually load? Runtime test results

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

Runtimerequire("env-paths")import "env-paths"
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✓ works✓ works

How to import env-paths

ES modules (import)

import envPaths from "env-paths";

CommonJS (require)

// Node.js 20.19+ / 22.12+ / newer (package has no top-level await):
const envPaths = require("env-paths");

// Any Node.js version:
const envPaths = await import("env-paths");

// Or pin the last CommonJS release:
// npm install env-paths@2.2.1

Module format by version

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

VersionsFormatFirst published
3.0.0 – 4.0.0ESM-onlyAug 27, 2021
0.1.0 – 2.2.1CommonJSJun 21, 2016

Frequently asked

Is env-paths ESM-only?

env-paths@4.0.0 is ESM-only. env-paths dropped its CommonJS build in 3.0.0 (August 2021). The last version you can require() on every Node.js version, including 18 and older, is 2.2.1, published Mar 8, 2021.

Which version of env-paths still supports CommonJS / require()?

2.2.1 is the last version of env-paths with a CommonJS build. Install it with "npm install env-paths@2.2.1". Every version from 3.0.0 on is ESM-only.

How do I use env-paths from a CommonJS file?

Use a dynamic import: const mod = await import("env-paths"). On Node.js 20.19+, 22.12+ and newer, a plain require("env-paths") also works for ESM packages that do not use top-level await. Alternatively pin env-paths@2.2.1.

Does env-paths work in Bun?

Yes. import "env-paths" loaded successfully in Bun 1.4 on Sep 9, 2026.

Does env-paths ship TypeScript types?

Yes. env-paths bundles its own type declarations; no @types package is needed.

Links

Other esm-only packages

Similar popularity