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. Markdown · 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 with a plain require()-able CommonJS entry is 2.2.1, published Mar 8, 2021; it declares support for Node.js >=6.

On Node.js 20.19+, 22.12+ and newer, require("env-paths") 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 env-paths@4.0.0 declares Node.js >=20, so 18 is outside its supported range anyway.

env-paths@4.0.0 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("env-paths") 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 envPaths = await import("env-paths"). 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 env-paths@2.2.1, the last CommonJS release (published Mar 8, 2021); it declares Node.js >=6.
  4. env-paths@4.0.0 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
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.0✓ works✓ works

How to import env-paths

ES modules (import)

import * as envPaths from "env-paths";

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 envPaths = require("env-paths");

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

// Or pin the last CommonJS release (declares Node.js >=6):
// 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, corrected where a runtime test of that version contradicted them (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 with a plain require()-able CommonJS entry is 2.2.1, published Mar 8, 2021; it declares support for Node.js >=6.

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

2.2.1 is the last version of env-paths with a CommonJS build; it declares Node.js >=6. 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?

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

Does env-paths work in Bun?

Yes. import "env-paths" loaded successfully in Bun 1.4.0 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