Bugs reach production. Fixwire finds them first: errors, traces, logs and AI agent runs in one place, an AI debugger on every plan, and your data kept in the region you choose.

fixwire-cli

The command line tool for Fixwire, run from your build or CI:

• Source maps: stamps each JavaScript file and its source map with a debug id, then uploads them, so Fixwire shows your original code in stack traces.
• Releases: records the commit a release was built from, so the AI debugger reads the right source and the diff from the previous release.
• Migration: moves a JavaScript or Python project from another error tracker's SDK to Fixwire's, and lists what's left to do by hand.

It is one static binary with no dependencies.

📦 Install

npm install --save-dev @fixwire/cli      # or pnpm add -D, yarn add -D; then npx fixwire-cli
go install github.com/fixwire/fixwire-cli@latest

Or download a binary for Linux, macOS or Windows (x64 and arm64) from the releases, and check it against checksums.txt.

⚙️ Settings

Flags win over the environment:

| Flag | Environment | | |---|---|---| | --url | FIXWIRE_URL | Your Fixwire API, e.g. https://api.eu.fixwire.io | | --auth-token | FIXWIRE_AUTH_TOKEN | An API key with the artifacts:write scope (source maps) or releases:write (releases) | | --org | FIXWIRE_ORG | Optional: the key names its organization | | --project | FIXWIRE_PROJECT | Optional: a key writes only to its own project; several, comma-separated | | --release | FIXWIRE_RELEASE | The release, as your SDK reports it |

The API key never appears in the tool's output, its usage text included.

🗺️ Source maps

After your build, before you deploy:

fixwire-cli sourcemaps inject dist
fixwire-cli sourcemaps upload dist

inject gives each built file that has a source map a debug id derived from its content, in the file and in its map (a "use strict" prologue or a hashbang stays first, and the map's columns move with it). A precompressed copy of a file it stamps is kept in step: <file>.gz is rewritten and <file>.br removed, so servers that send them (SvelteKit's adapter-node) don't send the old code. Fixwire's browser and Node SDKs report the debug ids with every error, so stack traces find their maps whatever the URL or the release.

upload sends every file and map in the directory as one bundle. A file already uploaded isn't sent again, so uploading the same build twice sends nothing. --inject stamps the files first, and --delete removes the maps once they're uploaded, so they aren't deployed with the build (Next.js serves whatever is in .next/static). Without debug ids, pass --release (and --dist): frames are then matched by release and URL, with --url-prefix the path the directory is served under (default ~/, any host).

🏷️ Releases

fixwire-cli releases set-commit --release [email protected]

records the commit at git rev-parse HEAD and the repository of the origin remote; --commit and --repository owner/name set them yourself.

🔀 Moving from another error tracker

fixwire-cli migrate .            # shows what it would change, and what's left
fixwire-cli migrate --write .    # changes it

migrate moves a JavaScript, TypeScript or Python project from another error tracker's SDK to Fixwire's: imports and requires (React's split between @fixwire/browser and @fixwire/react; Next.js, Vue, SvelteKit and Angular to their Fixwire packages), the few calls whose names differ (the Next.js config wrapper, SvelteKit's hooks and Vite plugin), package.json, requirements.txt, pyproject.toml, Pipfile and setup.cfg. Options and integrations Fixwire doesn't have are removed, so the project still type-checks and the SDK starts; Fixwire's Django middleware takes the place of the Django integration. Comments and strings are never touched, and a second run changes nothing.

It then lists what's left to do by hand, file and line: the DSN and the environment variables (FIXWIRE_DSN, FIXWIRE_RELEASE, FIXWIRE_ENVIRONMENT, with a framework's public prefix kept), Nuxt's module and config files, other frameworks to wire up yourself, bundler plugins to replace with sourcemaps upload --inject, and anything Fixwire doesn't do (session replay, profiling).

🤖 In CI

GitHub Actions, with FIXWIRE_AUTH_TOKEN as a secret:

- run: npm run build
- run: npx fixwire-cli sourcemaps upload --inject dist
  env:
    FIXWIRE_URL: https://api.eu.fixwire.io
    FIXWIRE_AUTH_TOKEN: ${{ secrets.FIXWIRE_AUTH_TOKEN }}
    FIXWIRE_RELEASE: web@${{ github.sha }}
- run: npx fixwire-cli releases set-commit
  env:
    FIXWIRE_URL: https://api.eu.fixwire.io
    FIXWIRE_AUTH_TOKEN: ${{ secrets.FIXWIRE_AUTH_TOKEN }}
    FIXWIRE_RELEASE: web@${{ github.sha }}

Contributing

Issues and pull requests are welcome: see CONTRIBUTING.md. Report security issues privately: see SECURITY.md.

License

MIT