canirequire

canirequire › CommonJS › @opentelemetry/instrumentation

Is @opentelemetry/instrumentation ESM-only? Can you require() it?

Base class for node which OpenTelemetry instrumentation modules extend

Last verified Sep 9, 2026 against @opentelemetry/instrumentation@0.222.0. Markdown · JSON

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

@opentelemetry/instrumentation ships CommonJS only. require("@opentelemetry/instrumentation") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js ^18.19.0 || >=20.6.0. import "@opentelemetry/instrumentation" 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("@opentelemetry/instrumentation") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js ^18.19.0 || >=20.6.0.
  2. From ES modules use the default import: import instrumentation from "@opentelemetry/instrumentation"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: types are bundled; install nothing extra.
Latest
0.222.0 (Aug 31, 2026)
Module format
CommonJS
Last CommonJS version
0.222.0
TypeScript types
Bundled
Node engines
^18.19.0 || >=20.6.0
Weekly downloads
89.3M
License
Apache-2.0

Does @opentelemetry/instrumentation@0.222.0 actually load? Runtime test results

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

Runtimerequire("@opentelemetry/instrumentation")import "@opentelemetry/instrumentation"
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 @opentelemetry/instrumentation

ES modules (import)

import instrumentation from "@opentelemetry/instrumentation";

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

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

VersionsFormatFirst published
0.35.0 – 0.222.0CommonJSJan 11, 2023

Frequently asked

Is @opentelemetry/instrumentation ESM-only?

@opentelemetry/instrumentation@0.222.0 is a CommonJS package. @opentelemetry/instrumentation ships CommonJS only. require("@opentelemetry/instrumentation") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js ^18.19.0 || >=20.6.0. import "@opentelemetry/instrumentation" 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 @opentelemetry/instrumentation with ES module syntax?

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

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

Does @opentelemetry/instrumentation ship TypeScript types?

Yes. @opentelemetry/instrumentation bundles its own type declarations; no @types package is needed.

Links

Other commonjs packages

Similar popularity