Packages

@opentelemetry/instrumentation-redis-4

0.49.0 · 2 Jun 2025Apache-2.06.9M / weekHomepagenpmAtom feed

Deprecated by its maintainers: Use "@opentelemetry/instrumentation-redis", which (as of v0.50.0) includes support for instrumenting redis v4.What to use instead
Your version

What to use instead

Named in the deprecation message

Read from the message, so worth a look before switching.

Before you switch

  1. 1

    Check what else depends on it

    Paste your package.json in the dependency check to see every deprecated or outdated package in one pass, not only this one.

  2. 2

    Read the replacement's peers and releases

    The page of @opentelemetry/instrumentation-redis lists what it works with, its recent release notes and any open advisory.

  3. 3

    Know when it ships

    Follow the new package on inlinr: its releases and advisories land in your feed, and the time spent on the migration branch shows on its page.

Latest releases

All 36 releases
  1. 0.49.x · latest line
  2. 0.49.0

    2 Jun 2025
  3. 0.48.x · maintenance
  4. 0.48.0

    15 May 2025
  5. 0.47.x · maintenance
  6. 0.47.0

    18 Mar 2025

Dependency tracking

Know when your own dependencies move

This page watches @opentelemetry/instrumentation-redis-4. inlinr reads your package.json and keeps the same watch on every dependency you declare, then tells you only what needs you.

  • Advisories reach you

    An email when a critical or high advisory affects a project, before the next install.

  • Upgrades checked first

    Peer ranges, Node, ESM-only and types changes read before you bump.

  • Only what matters

    Majors and breaking notes stay; patches and sibling bumps fold into one line.

How dependency tracking works

Registry facts last checked 21 Nov 2026. Releases and advisories last read 21 Nov 2026.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.