canirequire

canirequire › CommonJS › @opentelemetry/semantic-conventions

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

OpenTelemetry semantic conventions

Last verified Sep 9, 2026 against @opentelemetry/semantic-conventions@1.43.0. Markdown · JSON

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

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

Does @opentelemetry/semantic-conventions@1.43.0 actually load? Runtime test results

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

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

ES modules (import)

import semanticConventions from "@opentelemetry/semantic-conventions";

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

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

VersionsFormatFirst published
0.23.0 – 1.43.0CommonJSJun 30, 2021

Frequently asked

Is @opentelemetry/semantic-conventions ESM-only?

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

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

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

Does @opentelemetry/semantic-conventions ship TypeScript types?

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

Links

Other commonjs packages

Similar popularity