canirequire

canirequire › CommonJS › crypto

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

This package is no longer supported and has been deprecated. To avoid malicious use, npm is hanging on to the package name.

Last verified Sep 9, 2026 against crypto@1.0.1. Markdown · JSON

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

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

What to do

  1. require("crypto") 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 crypto from "crypto"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: no types are available for crypto; declare the module yourself if you need them.
  4. This package is deprecated: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
Latest
1.0.1 (Aug 10, 2017)
Module format
CommonJS
Last CommonJS version
1.0.1
TypeScript types
None
Node engines
not declared
Weekly downloads
1.4M
License
ISC

Deprecated: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.

Does crypto@1.0.1 actually load? Runtime test results

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

Runtimerequire("crypto")import "crypto"
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

ES modules (import)

import crypto from "crypto";

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 crypto = require("crypto");

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

VersionsFormatFirst published
0.0.1 – 1.0.1CommonJSApr 14, 2011

Frequently asked

Is crypto ESM-only?

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

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

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

Does crypto ship TypeScript types?

No. crypto ships no type declarations and there is no @types package for it.

Links

Other commonjs packages

Similar popularity