canirequire

canirequire › CommonJS › @opentelemetry/sdk-metrics

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

OpenTelemetry metrics SDK

Last verified Sep 9, 2026 against @opentelemetry/sdk-metrics@2.11.0. Markdown · JSON

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

@opentelemetry/sdk-metrics ships CommonJS only. require("@opentelemetry/sdk-metrics") 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/sdk-metrics" 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/sdk-metrics") 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 sdkMetrics from "@opentelemetry/sdk-metrics"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: types are bundled; install nothing extra.
Latest
2.11.0 (Aug 31, 2026)
Module format
CommonJS
Last CommonJS version
2.11.0
TypeScript types
Bundled
Node engines
^18.19.0 || >=20.6.0
Weekly downloads
44.3M
License
Apache-2.0

Does @opentelemetry/sdk-metrics@2.11.0 actually load? Runtime test results

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

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

ES modules (import)

import sdkMetrics from "@opentelemetry/sdk-metrics";

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

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

VersionsFormatFirst published
0.32.0 – 2.11.0CommonJSAug 24, 2022

Frequently asked

Is @opentelemetry/sdk-metrics ESM-only?

@opentelemetry/sdk-metrics@2.11.0 is a CommonJS package. @opentelemetry/sdk-metrics ships CommonJS only. require("@opentelemetry/sdk-metrics") 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/sdk-metrics" 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/sdk-metrics with ES module syntax?

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

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

Does @opentelemetry/sdk-metrics ship TypeScript types?

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

Links

Other commonjs packages

Similar popularity