# Is crypto-js ESM-only? Can you require() it?

> crypto-js@4.2.0 is a CommonJS package. CommonJS — require() works on every Node.js version we test.

JavaScript library of crypto standards.

Last verified Sep 9, 2026 against crypto-js@4.2.0.

crypto-js ships CommonJS only. require("crypto-js") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "crypto-js" 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:** Active development of CryptoJS has been discontinued. This library is no longer maintained.

## What to do

1. require("crypto-js") 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 cryptoJs from "crypto-js"; then destructure. Named imports only work when Node.js can statically detect the exports.
3. TypeScript: npm install -D @types/crypto-js
4. This package is deprecated: Active development of CryptoJS has been discontinued. This library is no longer maintained.

## Facts

- Latest: 4.2.0 (Oct 24, 2023)
- Module format: CommonJS
- Last CommonJS version: 4.2.0
- TypeScript types: @types/crypto-js
- Node engines: not declared
- Weekly downloads: 16.9M
- License: MIT

## Runtime test results for crypto-js@4.2.0

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

| Runtime | require("crypto-js") | import "crypto-js" |
|---|---|---|
| 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 crypto-js

ES modules:

```js
import cryptoJs from "crypto-js";
```

CommonJS:

```js
const cryptoJs = require("crypto-js");
```

## Module format by version

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

| Versions | Format | First published |
|---|---|---|
| 3.1.2 – 4.2.0 | CommonJS | May 7, 2013 |

## Frequently asked

**Is crypto-js ESM-only?**

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

Yes. import cryptoJs from "crypto-js" 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 crypto-js work in Bun?**

Yes. import "crypto-js" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

**Does crypto-js ship TypeScript types?**

Not bundled. Install the community types with "npm install -D @types/crypto-js".

## Links

- [crypto-js on npm](https://www.npmjs.com/package/crypto-js)
- [Source repository](https://github.com/brix/crypto-js)
- [HTML version](https://canirequire.com/package/crypto-js/)
- [JSON version](https://canirequire.com/package/crypto-js.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.