canirequire

canirequire › CommonJS › @img/sharp-libvips-linuxmusl-x64

Is @img/sharp-libvips-linuxmusl-x64 ESM-only? Can you require() it?

Prebuilt libvips and dependencies for use with sharp on Linux (musl) x64

Last verified Sep 9, 2026 against @img/sharp-libvips-linuxmusl-x64@1.3.3. Markdown · JSON

CommonJS CommonJS, subpaths only — require("@img/sharp-libvips-linuxmusl-x64/…") works, require("@img/sharp-libvips-linuxmusl-x64") does not

@img/sharp-libvips-linuxmusl-x64 exposes only subpaths in its exports map, for example "@img/sharp-libvips-linuxmusl-x64/lib"; there is no root entry, so require("@img/sharp-libvips-linuxmusl-x64") and import "@img/sharp-libvips-linuxmusl-x64" both throw ERR_PACKAGE_PATH_NOT_EXPORTED. The subpaths are CommonJS: require("@img/sharp-libvips-linuxmusl-x64/lib") works everywhere, and import "@img/sharp-libvips-linuxmusl-x64/lib" works through Node's CommonJS interop.

What to do

  1. Load subpaths, never the bare name: const sharpLibvipsLinuxmuslX64 = require("@img/sharp-libvips-linuxmusl-x64/lib"). require("@img/sharp-libvips-linuxmusl-x64") throws ERR_PACKAGE_PATH_NOT_EXPORTED.
  2. From ES modules use the default import: import sharpLibvipsLinuxmuslX64 from "@img/sharp-libvips-linuxmusl-x64/lib"; then destructure. Named imports only work when Node.js can statically detect the exports.
  3. TypeScript: no types are available for @img/sharp-libvips-linuxmusl-x64; declare the module yourself if you need them.
Latest
1.3.3 (Aug 26, 2026)
Module format
CommonJS
Last CommonJS version
1.3.3
TypeScript types
None
Node engines
not declared
Weekly downloads
45.5M
License
LGPL-3.0-or-later

Does @img/sharp-libvips-linuxmusl-x64@1.3.3 actually load? Runtime test results

Installed and executed on Sep 9, 2026 with require("@img/sharp-libvips-linuxmusl-x64") from a CommonJS file and import "@img/sharp-libvips-linuxmusl-x64" from an ES module.

Runtimerequire("@img/sharp-libvips-linuxmusl-x64")import "@img/sharp-libvips-linuxmusl-x64"
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 @img/sharp-libvips-linuxmusl-x64

ES modules (import)

import sharpLibvipsLinuxmuslX64 from "@img/sharp-libvips-linuxmusl-x64/lib";

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 sharpLibvipsLinuxmuslX64 = require("@img/sharp-libvips-linuxmusl-x64/lib");

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

VersionsFormatFirst published
0.0.1 – 1.3.3CommonJSOct 12, 2023

Frequently asked

Is @img/sharp-libvips-linuxmusl-x64 ESM-only?

@img/sharp-libvips-linuxmusl-x64@1.3.3 is a CommonJS package, reachable only through subpaths. @img/sharp-libvips-linuxmusl-x64 exposes only subpaths in its exports map, for example "@img/sharp-libvips-linuxmusl-x64/lib"; there is no root entry, so require("@img/sharp-libvips-linuxmusl-x64") and import "@img/sharp-libvips-linuxmusl-x64" both throw ERR_PACKAGE_PATH_NOT_EXPORTED. The subpaths are CommonJS: require("@img/sharp-libvips-linuxmusl-x64/lib") works everywhere, and import "@img/sharp-libvips-linuxmusl-x64/lib" works through Node's CommonJS interop.

Can I require @img/sharp-libvips-linuxmusl-x64?

Only by subpath. require("@img/sharp-libvips-linuxmusl-x64") throws ERR_PACKAGE_PATH_NOT_EXPORTED because the exports map has no root entry; require("@img/sharp-libvips-linuxmusl-x64/lib") works.

Can I import @img/sharp-libvips-linuxmusl-x64 with ES module syntax?

Yes. import sharpLibvipsLinuxmuslX64 from "@img/sharp-libvips-linuxmusl-x64/lib" 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 @img/sharp-libvips-linuxmusl-x64 work in Bun?

Importing @img/sharp-libvips-linuxmusl-x64 failed in Bun 1.4.0 on Sep 9, 2026: error: Cannot find module '@img/sharp-libvips-linuxmusl-x64' from '/Users/boat/Projects/top-seo/data/probe-work/@img__sharp-libvips-linuxmusl-x64/imp.mjs'

Does @img/sharp-libvips-linuxmusl-x64 ship TypeScript types?

No. @img/sharp-libvips-linuxmusl-x64 ships no type declarations and there is no @types package for it.

Links

Other commonjs packages

Similar popularity