canirequire › CommonJS › polished
Is polished ESM-only? Can you require() it?
A lightweight toolset for writing styles in Javascript.
Last verified Sep 9, 2026 against polished@4.3.1. Markdown · JSON
CommonJS CommonJS — require() works on every Node.js version we test
polished ships CommonJS only. require("polished") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=10. import "polished" 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
- require("polished") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=10.
- From ES modules use the default import: import polished from "polished"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: types are bundled; install nothing extra.
Does polished@4.3.1 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("polished") from a CommonJS file and import "polished" from an ES module.
| Runtime | require("polished") | import "polished" |
|---|---|---|
| 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 polished
ES modules (import)
import polished from "polished";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 polished = require("polished");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 (82 versions; the newest 60 shown).
| Versions | Format | First published |
|---|---|---|
| 1.8.2 – 4.3.1 | CommonJS | Nov 6, 2017 |
Frequently asked
Is polished ESM-only?
polished@4.3.1 is a CommonJS package. polished ships CommonJS only. require("polished") works on every Node.js version we test (18, 20, 22, 24 and 26) and in Bun. The package declares Node.js >=10. import "polished" 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 polished with ES module syntax?
Yes. import polished from "polished" 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 polished work in Bun?
Yes. import "polished" loaded successfully in Bun 1.4.0 on Sep 9, 2026.
Does polished ship TypeScript types?
Yes. polished bundles its own type declarations; no @types package is needed.
Links
Other commonjs packages
- debug 4.4.3CommonJS
- semver 7.8.5CommonJS
- ms 2.1.3CommonJS
- picomatch 4.0.7CommonJS
- ajv 8.20.0CommonJS
- source-map 0.8.0CommonJS
- react-is 19.2.8CommonJS
- readable-stream 4.7.0CommonJS
Similar popularity
- stylelint 17.15.0ESM-only
- js-beautify 2.0.3CommonJS
- webpack-node-externals 3.0.0CommonJS
- styled-components 6.5.3CommonJS
- firebase 12.18.0Dual
- @babel/plugin-proposal-nullish-coalescing-operator 7.18.6CommonJS
- @commitlint/config-conventional 21.2.2ESM-only
- xlsx 0.18.5CommonJS