canirequire

canirequire › CommonJS › @emotion/core

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

Last verified Sep 9, 2026 against @emotion/core@11.0.0. Markdown · JSON

CommonJS CommonJS on paper — require() failed in our runtime test

@emotion/core declares a CommonJS entry only, but require("@emotion/core") failed on every Node.js version in our probe: The `@emotion/core` package has been renamed to `@emotion/react`. Please import it like this `import { jsx } from '@emotion/react'`. import "@emotion/core" resolves to the same file, so it fails the same way. That usually means a missing peer dependency, a browser-only global, or a package that is not meant to be loaded directly; see the runtime table below.

What to do

  1. require("@emotion/core") failed in our probe on every Node.js version (The `@emotion/core` package has been renamed to `@emotion/react`. Please import it like this `import { jsx } from '@emotion/react'`); check the package README for peer dependencies or setup before relying on it.
  2. From ES modules use the default import: import core from "@emotion/core"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: types are bundled; install nothing extra.
Latest
11.0.0 (Nov 12, 2020)
Module format
CommonJS
Last CommonJS version
11.0.0
TypeScript types
Bundled
Node engines
not declared
Weekly downloads
1.1M
License
MIT

Does @emotion/core@11.0.0 actually load? Runtime test results

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

Runtimerequire("@emotion/core")import "@emotion/core"
Node.js 18✗ failsError✗ failsError
Node.js 20✗ failsError✗ failsError
Node.js 22✗ failsError✗ failsError
Node.js 24✗ failsError✗ failsError
Node.js 26✗ failsError✗ failsError
Bun 1.4.0✗ failsError✗ failsError

A failing require() on a CommonJS package usually means the package needs a browser/DOM global, a peer dependency, or a native binary that is not available in a bare Node.js process.

How to import @emotion/core

ES modules (import)

import core from "@emotion/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)

// require("@emotion/core") failed in our probe on every Node.js version we test (The `@emotion/core` package has been renamed to `@emotion/react`. Please import it like this `import { jsx } from '@emotion/react'`); see the runtime table.
const core = require("@emotion/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 (57 versions; the newest 57 shown).

VersionsFormatFirst published
0.0.4 – 11.0.0CommonJSFeb 9, 2018

Frequently asked

Is @emotion/core ESM-only?

@emotion/core@11.0.0 declares a CommonJS entry, but require() fails at runtime. @emotion/core declares a CommonJS entry only, but require("@emotion/core") failed on every Node.js version in our probe: The `@emotion/core` package has been renamed to `@emotion/react`. Please import it like this `import { jsx } from '@emotion/react'`. import "@emotion/core" resolves to the same file, so it fails the same way. That usually means a missing peer dependency, a browser-only global, or a package that is not meant to be loaded directly; see the runtime table below.

Can I require @emotion/core?

Not in practice. @emotion/core declares a CommonJS entry, but require("@emotion/core") failed on every Node.js version in our probe: The `@emotion/core` package has been renamed to `@emotion/react`. Please import it like this `import { jsx } from '@emotion/react'`. Check the package README for peer dependencies or setup before relying on it.

Can I import @emotion/core with ES module syntax?

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

Importing @emotion/core failed in Bun 1.4.0 on Sep 9, 2026: error: The `@emotion/core` package has been renamed to `@emotion/react`. Please import it like this `import { jsx } from '@emotion/react'`.

Does @emotion/core ship TypeScript types?

Yes. @emotion/core bundles its own type declarations; no @types package is needed.

Links

Other commonjs packages

Similar popularity