npm packages with breaking changes

• ● Breaking

  Stripe: API version 2025-03-31.basil restructures subscription & invoice fields

  The 2025-03-31.basil API version moves several billing fields (including subscription current_period_end to the subscription item) — pinned older SDKs read them from the old location. Upgrade the SDK and re-test billing flows.

  published 2025-03-31 · affects ≥ 12.0.0

  Source ↗
• ● Breaking

  Auth0: @auth0/nextjs-auth0 v4 reworks the App Router integration

  The v4 SDK restructured configuration and middleware for the App Router; v3 setup (handleAuth, getSession signatures) changes. Upgrading requires config and import updates.

  published 2025-01-20 · affects ≥ 3.0.0

  Source ↗
• ● BreakingAction required

  React: React 19 removes defaultProps for functions, string refs, legacy context

  React 19 removed defaultProps on function components (use default parameters), string refs, legacy context, and the react-dom render() / hydrate() APIs. Older code paths break on upgrade.

  published 2024-12-05 · affects ≥ 19.0.0

  Source ↗
• ▲ DeprecationAction required

  AWS SDK: AWS SDK for JavaScript v2 entered maintenance mode; end of support set

  aws-sdk (v2) is in maintenance mode and reaches end-of-support; AWS recommends migrating to the modular @aws-sdk/* v3 packages. No new features or non-critical fixes land on v2.

  published 2024-11-15 · sunsets 2025-09-08 · affects ≥ 2.0.0

  Source ↗
• ● BreakingAction required

  Next.js: Next 15: cookies(), headers(), params & searchParams are now async

  Next.js 15 made request APIs (cookies, headers, draftMode) and the params/searchParams props asynchronous. Synchronous access still works with a warning but is removed on the next major.

  published 2024-10-21 · affects ≥ 15.0.0

  Source ↗
• ▲ DeprecationAction required

  Shopify: REST Admin API marked legacy; GraphQL is the primary API

  Shopify designated the REST Admin API as legacy and now ships new features only on GraphQL. Public-app requirements and per-quarter version drops mean REST integrations need a GraphQL migration plan.

  published 2024-10-01 · sunsets 2025-04-01

  Source ↗
• ● BreakingAction required

  Google Cloud / Firebase: Firebase Dynamic Links shut down

  Firebase Dynamic Links has been sunset; existing links stop resolving after the shutdown date. Migrate deep-linking to an alternative (App Links / Universal Links or a third-party).

  published 2024-08-25 · sunsets 2025-08-25

  Source ↗
• ● BreakingAction required

  Twilio: Programmable Chat / older messaging endpoints reach end of life

  Twilio has sunset Programmable Chat (superseded by Conversations) and retired several legacy messaging endpoints. Calls to the removed endpoints now fail.

  published 2024-08-01 · sunsets 2025-09-30 · affects ≥ 3.0.0

  Source ↗
• ● Breaking

  Algolia: algoliasearch v5 changes client init & method names

  algoliasearch v5 (unified API client) changed client construction and renamed several methods; v4 code does not run against v5 without changes.

  published 2024-07-01 · affects ≥ 4.0.0

  Source ↗
• ▲ DeprecationAction required

  Anthropic: Claude 1 & 2 models retired; migrate to Claude 3/4 family

  Older Claude 1.x/2.x and claude-instant models were deprecated and retired. Move to a current model id (e.g. claude-haiku-4-5, claude-sonnet-4-5) on the Messages API.

  published 2024-06-27 · sunsets 2025-07-21

  Source ↗
• ▲ DeprecationAction required

  Vercel: Node.js 16 & 18 runtimes deprecated for Functions

  Vercel deprecated the Node.js 16 runtime and set an end date for 18.x; deployments must move to Node 20+. Builds pinned to old runtimes will fail after the cutoff.

  published 2024-06-01 · sunsets 2025-08-01

  Source ↗
• ▲ DeprecationAction required

  Stripe: Sources API deprecated in favor of PaymentIntents & PaymentMethods

  Stripe has deprecated the legacy Sources API; new integrations should use PaymentIntents/PaymentMethods. Existing Sources continue to work but receive no new features and should be migrated.

  published 2024-05-01 · sunsets 2026-12-31

  Source ↗
• ▲ Deprecation

  Redis: Redis relicensed (RSALv2/SSPL); OSS BSD build forked to Valkey

  Redis moved from BSD to source-available licensing (RSALv2/SSPL), prompting the Valkey fork. Self-hosting under the old OSS terms or redistributing may require re-evaluating your license posture.

  published 2024-03-20

  Source ↗
• ▲ Deprecation

  Anthropic: Legacy Text Completions API deprecated in favor of Messages API

  The /v1/complete Text Completions endpoint is legacy; the Messages API is the supported path. Older SDK versions default to the legacy client.

  published 2024-03-04 · affects ≥ 0.4.0

  Source ↗
• ▲ DeprecationApprox. date

  Slack: Legacy tokens & RTM API deprecated for new apps

  Slack deprecated legacy custom-integration tokens and steers new apps off the RTM API toward the Events API + Socket Mode. Legacy-token integrations should migrate before they are disabled.

  published 2024-03-01

  Source ↗
• ▲ DeprecationAction required

  Supabase: @supabase/auth-helpers deprecated in favor of @supabase/ssr

  The auth-helpers packages are deprecated; Supabase recommends migrating to @supabase/ssr for cookie-based auth in server frameworks. The old package receives no further updates.

  published 2024-02-15 · affects ≥ 0.0.0

  Source ↗
• ▲ Deprecation

  OpenAI: text-embedding-ada-002 superseded by text-embedding-3-*

  Newer embedding models (text-embedding-3-small/large) are cheaper and higher quality; ada-002 remains available but is no longer recommended for new work.

  published 2024-01-25

  Source ↗
• ▲ DeprecationAction requiredApprox. date

  SendGrid (Twilio): Sender authentication (SPF/DKIM) required; unauthenticated sending restricted

  Following Gmail/Yahoo bulk-sender rules, SendGrid tightened sender-authentication requirements; unauthenticated or non-compliant sending is throttled or blocked. Verify domain authentication.

  published 2023-12-01 · sunsets 2024-02-01

  Source ↗
• ● Breaking

  MongoDB: Node driver v6 drops callback API and older Node versions

  mongodb v6 removed the legacy callback-style API (promises only) and raised the minimum Node version. Callback-based code in v4/v5 will not compile against v6.

  published 2023-08-28 · affects ≥ 4.0.0

  Source ↗
• ● Breaking

  Prisma: Prisma 5 removed rejectOnNotFound; adds new engine defaults

  Prisma 5 removed the rejectOnNotFound option (use findUniqueOrThrow / findFirstOrThrow) and changed defaults. Prisma 4 code relying on rejectOnNotFound breaks.

  published 2023-07-11 · affects ≥ 4.0.0

  Source ↗
• ● BreakingAction required

  OpenAI: Legacy Completions models (text-davinci-003, etc.) shut down

  The GPT-3-era Completions models were shut down; requests to them now error. Migrate to the Chat Completions or Responses API with a current model.

  published 2023-07-06 · sunsets 2024-01-04 · affects ≥ 3.0.0

  Source ↗
• ▲ Deprecation

  Datadog: Datadog Agent v5 end of life

  Datadog Agent v5 reached end of life; hosts must run Agent v7. Old agents stop receiving updates and some integrations no longer report.

  published 2023-06-01 · sunsets 2024-01-01

  Source ↗
• ▲ Deprecation

  Next.js: App Router: getInitialProps / getServerSideProps not supported in app/

  In the App Router (default since 14), the legacy data-fetching methods do not run; server components + fetch replace them. Pages-router code moved into app/ silently loses data fetching.

  published 2023-05-04 · affects ≥ 13.4.0

  Source ↗
• ● Breaking

  Supabase: supabase-js v1 → v2 changed auth() and error handling

  supabase-js v2 reorganized the auth namespace and standardized { data, error } returns. v1 code will not run against the v2 client.

  published 2023-01-10 · affects ≥ 1.0.0

  Source ↗
• ● Breaking

  Cloudflare: Wrangler v1 deprecated; v2/v3 change config and service-worker syntax

  Wrangler v1 is deprecated and unsupported; v2+ changed wrangler.toml and pushes the Module Worker format over the legacy Service Worker syntax. v1 projects need config + entrypoint changes.

  published 2022-11-01 · affects ≥ 1.0.0

  Source ↗
• ● Breaking

  Google Cloud / Firebase: Firebase JS SDK v8 namespaced API removed in v9+ modular SDK

  The compat/namespaced firebase v8 API was superseded by the tree-shakeable modular v9 SDK; v8-style imports do not work against v10/v11 without the compat layer.

  published 2021-08-01 · affects ≥ 8.0.0

  Source ↗

Powered by ChangelogRadar's deprecation & pricing archive · An Atlas Project. Curated best-effort from public sources; not authoritative — verify with the vendor before acting.