canirequire › CommonJS › @tailwindcss/oxide-linux-x64-musl
Is @tailwindcss/oxide-linux-x64-musl ESM-only? Can you require() it?
Last verified Sep 9, 2026 against @tailwindcss/oxide-linux-x64-musl@4.3.3. Markdown · JSON
CommonJS CommonJS on paper — require() failed in our runtime test
@tailwindcss/oxide-linux-x64-musl declares a CommonJS entry only, but require("@tailwindcss/oxide-linux-x64-musl") failed on every Node.js version in our probe: Cannot find module '@tailwindcss/oxide-linux-x64-musl'. import "@tailwindcss/oxide-linux-x64-musl" 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
- require("@tailwindcss/oxide-linux-x64-musl") failed in our probe on every Node.js version (Cannot find module '@tailwindcss/oxide-linux-x64-musl'); check the package README for peer dependencies or setup before relying on it.
- From ES modules use the default import: import oxideLinuxX64Musl from "@tailwindcss/oxide-linux-x64-musl"; then destructure. Named imports only work when Node.js can statically detect the exports.
- TypeScript: no types are available for @tailwindcss/oxide-linux-x64-musl; declare the module yourself if you need them.
Does @tailwindcss/oxide-linux-x64-musl@4.3.3 actually load? Runtime test results
Installed and executed on Sep 9, 2026 with require("@tailwindcss/oxide-linux-x64-musl") from a CommonJS file and import "@tailwindcss/oxide-linux-x64-musl" from an ES module.
| Runtime | require("@tailwindcss/oxide-linux-x64-musl") | import "@tailwindcss/oxide-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.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 @tailwindcss/oxide-linux-x64-musl
ES modules (import)
import oxideLinuxX64Musl from "@tailwindcss/oxide-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)
// require("@tailwindcss/oxide-linux-x64-musl") failed in our probe on every Node.js version we test (Cannot find module '@tailwindcss/oxide-linux-x64-musl'); see the runtime table.
const oxideLinuxX64Musl = require("@tailwindcss/oxide-linux-x64-musl");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).
| Versions | Format | First published |
|---|---|---|
| 4.0.0 – 4.3.3 | CommonJS | Jan 21, 2025 |
Frequently asked
Is @tailwindcss/oxide-linux-x64-musl ESM-only?
@tailwindcss/oxide-linux-x64-musl@4.3.3 declares a CommonJS entry, but require() fails at runtime. @tailwindcss/oxide-linux-x64-musl declares a CommonJS entry only, but require("@tailwindcss/oxide-linux-x64-musl") failed on every Node.js version in our probe: Cannot find module '@tailwindcss/oxide-linux-x64-musl'. import "@tailwindcss/oxide-linux-x64-musl" 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 @tailwindcss/oxide-linux-x64-musl?
Not in practice. @tailwindcss/oxide-linux-x64-musl declares a CommonJS entry, but require("@tailwindcss/oxide-linux-x64-musl") failed on every Node.js version in our probe: Cannot find module '@tailwindcss/oxide-linux-x64-musl'. Check the package README for peer dependencies or setup before relying on it.
Can I import @tailwindcss/oxide-linux-x64-musl with ES module syntax?
Yes. import oxideLinuxX64Musl from "@tailwindcss/oxide-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 @tailwindcss/oxide-linux-x64-musl work in Bun?
Importing @tailwindcss/oxide-linux-x64-musl failed in Bun 1.4.0 on Sep 9, 2026: error: Cannot find module '@tailwindcss/oxide-linux-x64-musl' from '/Users/boat/Projects/top-seo/data/probe-work/@tailwindcss__oxide-linux-x64-musl/imp.mjs'
Does @tailwindcss/oxide-linux-x64-musl ship TypeScript types?
No. @tailwindcss/oxide-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
- jest-validate 30.5.1Dual
- isobject 4.1.1CommonJS
- proc-log 7.0.0CommonJS
- safe-stable-stringify 2.5.0Dual
- @colors/colors 1.6.1CommonJS
- axobject-query 4.1.0CommonJS
- @radix-ui/react-use-previous 1.1.4Dual
- babel-plugin-polyfill-corejs3 1.0.0ESM-only