canirequire

canirequire › CommonJS › @popperjs/core

Is @popperjs/core ESM-only? Can you require() it?

Tooltip and Popover Positioning Engine

Last verified Sep 9, 2026 against @popperjs/core@2.11.8. Markdown · JSON

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

@popperjs/core ships CommonJS only. require("@popperjs/core") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. import "@popperjs/core" 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("@popperjs/core") 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 core from "@popperjs/core"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: no types are available for @popperjs/core; declare the module yourself if you need them.
Latest
2.11.8 (May 26, 2023)
Module format
CommonJS
Last CommonJS version
2.11.8
Native ESM since
2.10.0
TypeScript types
None
Node engines
not declared
Weekly downloads
21.2M
License
MIT

Does @popperjs/core@2.11.8 actually load? Runtime test results

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

Runtimerequire("@popperjs/core")import "@popperjs/core"
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 @popperjs/core

ES modules (import)

import core from "@popperjs/core";

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

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

VersionsFormatFirst published
2.10.1 – 2.11.8CommonJSSep 3, 2021
2.10.0Dual (CommonJS + ESM)Sep 2, 2021
2.0.0 – 2.9.3CommonJSJan 22, 2020

Frequently asked

Is @popperjs/core ESM-only?

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

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

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

Does @popperjs/core ship TypeScript types?

No. @popperjs/core ships no type declarations and there is no @types package for it.

Links

Other commonjs packages

Similar popularity