Keeping Blipit up to date

1What updates on its own

• Script tag from https://blipit.io/sdk/blipit.js: always the newest version.
• Odoo: the module loads the newest browser SDK after its next sync with Blipit. When a new blipit_monitor version is out, administrators see an update bar at the top of every Odoo screen with the steps.
• Since @blipit/browser 0.3.11, npm installs and script tags that name a version (https://blipit.io/sdk/0.3.11/blipit.js) load the reporter, the Report a bug button, the feedback form and session replay from https://blipit.io/sdk/0.3/, which always holds the newest compatible 0.3 build. Your installed core tells each part its version; a part that does not support that core refuses to run and the exact version is loaded instead, so nothing breaks.
• Everything else (the core in your bundle, @blipit/nextjs, @blipit/node, React Native, Python, PHP, Ruby, Go, Java, .NET, Swift, Flutter) changes only when you update the package.

2Pin the exact version

To load every part from the exact version you installed, pass sdkChannel: "exact" to init. Use it when your security policy needs Subresource Integrity: an integrity hash only works on an exact-version path such as https://blipit.io/sdk/0.3.11/blipit-report.js, because the 0.3 path changes with every release. Exact-version files never change once published; every path is served from blipit.io.

Blipit.init({
  key: "blipit_pk_...",
  sdkChannel: "exact",
});

3The update banner

Blipit sees which SDK and version each project sent events with in the last 7 days. When a newer release is out, the project page and the projects list show a banner such as: This project uses @blipit/browser 0.3.7, 0.3.11 is available, with what changed since your version and the update command for your stack (npm, pnpm, yarn, pip, composer and so on) with a Copy button. The cross hides it for that version only; the next release shows it again.

4Emails when it matters

Releases marked important or security fix send one email to the workspace owners, only for projects that sent events from an affected version in the last 14 days, and at most once per release and project. Normal releases only show the banner. To stop these emails, turn off Email me when an SDK update fixes something important in Settings, or use the link at the bottom of the email.

5The notice in your development console

In development, each SDK prints one line per session or process when a newer version is out. It reads the newest version from a reply the SDK already gets from Blipit, so it adds no request, and it is never shown in production or to your visitors.

• Browser and Next.js: on localhost, 127.0.0.1 and .local hosts, with debug: true, or when NODE_ENV is development. It comes with the Report a bug settings, so with feedbackWidget: false there is no notice.
• Node, Python, PHP, Ruby and Go: when the environment is development or debug is on.
• React Native: in __DEV__ builds.

[blipit] 0.3.11 is available (you have 0.3.7) — Loads the newest compatible bug reporter automatically… — npm install @blipit/browser@latest

6Update commands

npm install @blipit/browser@latest
npm install @blipit/nextjs@latest
npm install @blipit/node@latest
npm install @blipit/react-native@latest

pnpm add @blipit/browser@latest

yarn add @blipit/browser@latest

pip install -U blipit

composer update blipit/blipit

bundle update blipit

go get github.com/blipit-io/blipit-go@latest

dotnet add package Blipit

<script src="https://blipit.io/sdk/0.3.11/blipit.js" defer></script>

Good to know

• pnpm 11 waits a day before it installs a new release (minimum-release-age), so on release day pnpm add quietly installs the previous version. Try again tomorrow, run pnpm add @blipit/browser@<version> --config.minimum-release-age=0, or add @blipit/* to minimumReleaseAgeExclude in pnpm-workspace.yaml.
• Blipit cannot see the installed version yet for .NET, Java, Android, Swift and Flutter, or for Python, PHP, Ruby, Go and React Native before 0.2.1, so those projects get no banner or email. Update to 0.2.1 or later to get them.