canirequire

canirequire › CommonJS › @tailwindcss/oxide

Is @tailwindcss/oxide ESM-only? Can you require() it?

Last verified Sep 9, 2026 against @tailwindcss/oxide@4.3.3. Markdown · JSON

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

@tailwindcss/oxide ships CommonJS only. require("@tailwindcss/oxide") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 20. import "@tailwindcss/oxide" 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.

What to do

  1. require("@tailwindcss/oxide") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >= 20.
  2. From ES modules use the default import: import oxide from "@tailwindcss/oxide"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: types are bundled; install nothing extra.
Latest
4.3.3 (Jul 16, 2026)
Module format
CommonJS
Last CommonJS version
4.3.3
TypeScript types
Bundled
Node engines
>= 20
Weekly downloads
58.7M
License
MIT

Does @tailwindcss/oxide@4.3.3 actually load? Runtime test results

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

Runtimerequire("@tailwindcss/oxide")import "@tailwindcss/oxide"
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 @tailwindcss/oxide

ES modules (import)

import oxide from "@tailwindcss/oxide";

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

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

VersionsFormatFirst published
4.0.0 – 4.3.3CommonJSJan 21, 2025

Frequently asked

Is @tailwindcss/oxide ESM-only?

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

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

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

Does @tailwindcss/oxide ship TypeScript types?

Yes. @tailwindcss/oxide bundles its own type declarations; no @types package is needed.

Links

Other commonjs packages

Similar popularity