canirequire

canirequire › CommonJS › history

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

Manage session history with JavaScript

Last verified Sep 9, 2026 against history@5.3.0. Markdown · JSON

CommonJS CommonJS — require() works on every Node.js version we test

history ships CommonJS only. require("history") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "history" 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.

It also declares a "module" field, so bundlers such as webpack, Vite and esbuild pick up an ESM build for tree-shaking.

What to do

  1. require("history") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun.
  2. From ES modules use the default import: import history from "history"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: types are bundled; install nothing extra.
Latest
5.3.0 (Feb 22, 2022)
Module format
CommonJS
Last CommonJS version
5.3.0
TypeScript types
Bundled
Node engines
not declared
Weekly downloads
10.2M
License
MIT

Does history@5.3.0 actually load? Runtime test results

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

Runtimerequire("history")import "history"
Node.js 18✓ works✓ 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 history

ES modules (import)

import history from "history";

Named imports from a CommonJS package only work when Node.js can statically detect them. If a named import fails, use the default import and destructure.

CommonJS (require)

const history = require("history");

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 (79 versions; the newest 60 shown).

VersionsFormatFirst published
1.8.4 – 5.3.0CommonJSAug 31, 2015

Frequently asked

Is history ESM-only?

history@5.3.0 is a CommonJS package. history ships CommonJS only. require("history") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "history" 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 history with ES module syntax?

Yes. import history from "history" 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 history work in Bun?

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

Does history ship TypeScript types?

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

Links

Other commonjs packages

Similar popularity