Install

It installs as a devDependency, but the mount component that renders <Blix /> imports it from your application code — so any build that drops devDependencies before the build step (npm ci --omit=dev, pnpm install --prod, the usual shape of a multi-stage Docker image) fails while resolving that import. devDependencies have to be present at build time. Dropping them from the final runtime image is fine: nothing from Blix reaches the production output anyway.

The package ships ESM only. Both entry points declare "types" and "import" in exports, with no "require" and no "default" fallback, so require("@hakam-aldeen-kh/blix") and CJS-only tooling — an older Jest config is the usual one — fail with ERR_PACKAGE_PATH_NOT_EXPORTED. That is by design, not a packaging bug: a dev tool that is eliminated from production has no reason to carry a second build output.

Peer dependencies

react and react-dom (v18 or v19) are required. axios, @reduxjs/toolkit and @tanstack/react-query are optional peers — you only need the ones whose capture you actually use. The capture layer is structurally typed against each of them and imports none of them — not at runtime, and not in its published type declarations — so installing Blix does not pull a data-fetching or state library into your tree, and your type-check never goes looking for one.

axios is optional, and fetch-only apps are fully supported. An app that calls fetch directly — the default in a Next.js App Router project — captures its HTTP traffic with attachFetchMonitor and never needs axios installed, not even for types.