canirequire › CommonJS › lightningcss-linux-x64-musl
Is lightningcss-linux-x64-musl ESM-only? Can you require() it?
A CSS parser, transformer, and minifier written in Rust
Last verified Sep 9, 2026 against lightningcss-linux-x64-musl@1.33.0. JSON
CommonJS CommonJS — require() works on every Node.js version
lightningcss-linux-x64-musl ships CommonJS only. require("lightningcss-linux-x64-musl") works everywhere. import "lightningcss-linux-x64-musl" 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.
Does lightningcss-linux-x64-musl@1.33.0 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("lightningcss-linux-x64-musl") from a CommonJS file and import "lightningcss-linux-x64-musl" from an ES module.
| Runtime | require("lightningcss-linux-x64-musl") | import "lightningcss-linux-x64-musl" |
|---|---|---|
| Node.js 18 | ✗ failsMODULE_NOT_FOUND | ✗ failsERR_MODULE_NOT_FOUND |
| Node.js 20 | ✗ failsMODULE_NOT_FOUND | ✗ failsERR_MODULE_NOT_FOUND |
| Node.js 22 | ✗ failsMODULE_NOT_FOUND | ✗ failsERR_MODULE_NOT_FOUND |
| Node.js 24 | ✗ failsMODULE_NOT_FOUND | ✗ failsERR_MODULE_NOT_FOUND |
| Node.js 26 | ✗ failsMODULE_NOT_FOUND | ✗ failsERR_MODULE_NOT_FOUND |
| Bun 1.4 | ✗ failserror: Cannot find package 'lightningcss-linux-x64-musl' from '/Users/boat/Projects/top-seo/data/probe-work/lightningcss-linux-x64-musl/req.cjs' | ✗ failserror: Cannot find package 'lightningcss-linux-x64-musl' from '/Users/boat/Projects/top-seo/data/probe-work/lightningcss-linux-x64-musl/imp.mjs' |
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 lightningcss-linux-x64-musl
ES modules (import)
import lightningcssLinuxX64Musl from "lightningcss-linux-x64-musl";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 lightningcssLinuxX64Musl = require("lightningcss-linux-x64-musl");Module format by version
Derived from the type, main and exports fields of every stable release on npm (42 versions; the newest 42 shown).
| Versions | Format | First published |
|---|---|---|
| 1.14.0 – 1.33.0 | CommonJS | Sep 8, 2022 |
Frequently asked
Is lightningcss-linux-x64-musl ESM-only?
lightningcss-linux-x64-musl@1.33.0 is a CommonJS package. lightningcss-linux-x64-musl ships CommonJS only. require("lightningcss-linux-x64-musl") works everywhere. import "lightningcss-linux-x64-musl" 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 lightningcss-linux-x64-musl with ES module syntax?
Yes. import lightningcssLinuxX64Musl from "lightningcss-linux-x64-musl" 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 lightningcss-linux-x64-musl work in Bun?
Importing lightningcss-linux-x64-musl failed in Bun 1.4 on Sep 9, 2026: error: Cannot find package 'lightningcss-linux-x64-musl' from '/Users/boat/Projects/top-seo/data/probe-work/lightningcss-linux-x64-musl/imp.mjs'
Does lightningcss-linux-x64-musl ship TypeScript types?
No. lightningcss-linux-x64-musl ships no type declarations and there is no @types package for it.
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
- html-encoding-sniffer 6.0.0CommonJS
- path-is-absolute 2.0.0CommonJS
- postcss-value-parser 4.2.0CommonJS
- saxes 6.0.0CommonJS
- deepmerge 4.3.1CommonJS
- possible-typed-array-names 1.1.0CommonJS
- domelementtype 3.0.0ESM-only
- merge2 1.4.1CommonJS