Troubleshooting

General Issues

Layout is not correct

Set the drawDebugBorder option to outline every node.

import { ImageResponse } from "takumi-js/response";

export function GET() {
  return new ImageResponse(<></>, {
    width: 100,
    height: 100,
    drawDebugBorder: true,
    // ...
  });
}

If the issue persists, file an issue on our GitHub repository.

Node.js Issues

Cannot find native binding

@takumi-rs/core loads a platform-specific native package. This error means the package for the current platform is missing.

Hoist the native package

If you are using a package manager with virtual store such as pnpm or yarn, allow it to hoist the native binary. The following examples are for pnpm; after updating the configuration, re-run pnpm i.

publicHoistPattern:
  - "@takumi-rs/core-*"

With pnpm versions earlier than 10.5.0, add the equivalent setting to .npmrc instead:

public-hoist-pattern[]=@takumi-rs/core-*

For other package managers, refer to their docs for hoist config instructions.

Install the native package for your deploy target

Package managers only install the native package matching the machine that runs the install. Installing on one platform and deploying to another — for example installing on macOS and deploying to a Linux server — leaves the target's native package missing.

Install the package for the deploy target explicitly:

npm install @takumi-rs/core-linux-x64-gnu

Pick the package matching the target platform:

TypeError: fetch failed

Node.js fetch (via undici) can drop the socket while loading a remote img URL (#349). Pass the image as a base64 data URL so Takumi skips the fetch.