canirequire

canirequire › CommonJS › @colors/colors

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

get colors in your node.js console

Last verified Sep 9, 2026 against @colors/colors@1.6.1. Markdown · JSON

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

@colors/colors ships CommonJS only. require("@colors/colors") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=0.1.90. import "@colors/colors" 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("@colors/colors") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=0.1.90.
  2. From ES modules use the default import: import colors from "@colors/colors"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: no types are available for @colors/colors; declare the module yourself if you need them.
Latest
1.6.1 (Sep 7, 2026)
Module format
CommonJS
Last CommonJS version
1.6.1
TypeScript types
None
Node engines
>=0.1.90
Weekly downloads
52.0M
License
MIT

Does @colors/colors@1.6.1 actually load? Runtime test results

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

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

ES modules (import)

import colors from "@colors/colors";

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

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

VersionsFormatFirst published
1.4.0 – 1.6.1CommonJSFeb 12, 2022

Frequently asked

Is @colors/colors ESM-only?

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

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

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

Does @colors/colors ship TypeScript types?

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

Links

Other commonjs packages

Similar popularity