SAVED COMPATIBILITY REPORT

sharp@0.35.5
on Bun

Analyzed October 12, 2026 at 9:41 AM UTC · Static analysis only

A saved snapshot, not a live compatibility guarantee. Opening this page does not run a scan.

Analyze a package ↗Methodology and limitations

What compatibility issues were found on Bun?

The saved analysis assesses sharp@0.35.5 as unknown for Bun. Review the findings and coverage below; this is not a runtime execution test.

Unknown

Not scored · low confidence

No detected blocker within scan limits does not mean verified execution. Scores are heuristics, not probabilities.

Score withheld: inspection is incomplete or runtime support is unresolved.

Assessment assumptions

Broad runtime profile; no exact runtime version, platform, or deployment configuration was selected.
Package declares Node.js >=20.9.0. This constraint has not been checked against a selected version and does not declare Bun or Deno support.
Bun supports Node-API addons, not every Node/V8 addon. Node-API symbol detection does not verify API coverage, ABI version, or platform binaries.

import: Unknown
execute: Unknown
APIs: Unknown
SSR: Unknown

26 packages and 124 files scanned. Dependency graph inspection was capped. At least one file scan was incomplete. Coverage describes the inspected scope, not every possible code path.

FILE AND DEPENDENCY EVIDENCE

1 finding to review

1. Dynamic require

Unknown

Computed require() cannot be resolved statically

Source excerpt

dist/libvips.mjs:54:12 · first detected occurrence

  52const buildSharpLibvipsIncludeDir = () => {
  53  try {
› 54    return require(`@img/sharp-libvips-dev-${buildPlatformArch()}/include`);
  55  } catch {
  56    try {

Suggested next steps

Make the possible imports explicit

First trace whether this file is reachable from the entry point your application uses. The finding may be outside the executed code path.
Identify the possible values passed to require() and check whether the target loader or bundler can include them.
If you control the source, replace computed paths with a bounded map of literal imports where practical. Otherwise, use the package's documented bundler integration or request an upstream fix.

Rebuild and exercise the affected import and operation in your exact runtime, version, and deployment configuration. These suggestions are not a tested fix.

Node.js package entry points and conditional exports ↗

File: dist/libvips.mjs
Dependency path: sharp@0.35.5
Entry points: dist/index.mjs
Dimension: import
Reachability: not proven reachable from selected entry
Confidence: low · static

How to use this report

This report preserves the findings as of October 12, 2026 at 9:41 AM UTC. It may use older analysis rules (analysis version 4). Package code was not executed. Runtime versions, flags, bundlers, and operating systems can change actual compatibility.

Reachability is approximate. Optional dependencies, generated code, dynamic imports, and incomplete scans can cause false positives or missed issues. A green assessment means no blocker was found within the inspected scope. The score is a heuristic, not a probability.

Read all limitations ↗

sharp@0.35.5on Bun