canirequire

canirequire › CommonJS › @ethersproject/networks

Is @ethersproject/networks ESM-only? Can you require() it?

Network definitions for ethers.

Last verified Sep 9, 2026 against @ethersproject/networks@5.8.0. Markdown · JSON

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

@ethersproject/networks ships CommonJS only. require("@ethersproject/networks") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "@ethersproject/networks" 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("@ethersproject/networks") 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 networks from "@ethersproject/networks"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: types are bundled; install nothing extra.
Latest
5.8.0 (Feb 26, 2025)
Module format
CommonJS
Last CommonJS version
5.8.0
TypeScript types
Bundled
Node engines
not declared
Weekly downloads
1.6M
License
MIT

Does @ethersproject/networks@5.8.0 actually load? Runtime test results

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

Runtimerequire("@ethersproject/networks")import "@ethersproject/networks"
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 @ethersproject/networks

ES modules (import)

import networks from "@ethersproject/networks";

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 networks = require("@ethersproject/networks");

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

VersionsFormatFirst published
5.0.0 – 5.8.0CommonJSJun 13, 2020

Frequently asked

Is @ethersproject/networks ESM-only?

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

Yes. import networks from "@ethersproject/networks" 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 @ethersproject/networks work in Bun?

Yes. import "@ethersproject/networks" loaded successfully in Bun 1.4.0 on Sep 9, 2026.

Does @ethersproject/networks ship TypeScript types?

Yes. @ethersproject/networks bundles its own type declarations; no @types package is needed.

Links

Other commonjs packages

Similar popularity