node-auth0 v7.0.0 : Announcement and changes

[tusharpandey13]

node-auth0 v7.0.0 is now generally available.

🧭 What changed

• node-auth0 v7 is Management-API-only. It's the ManagementClient you already use, nothing more.
• The authentication layer (AuthenticationClient, UserInfoClient) is no longer part of node-auth0. Authentication now lives in @auth0/auth0-auth-js and @auth0/auth0-server-js.

🙂 If you only use the Management API

There are no breaking changes for your usage. The ManagementClient API surface is unchanged from v6. Upgrading to v7 should be a version bump.

🔐 If you use AuthenticationClient / UserInfoClient

This is the part that moves. The migration guide maps every method to its equivalent in the new authentication SDKs, and we ship tooling to automate most of it (see below).

🧩 Why we did this

We wanted to separate the authentication layer from the management layer, and there are a few reasons that matter for you, not just us:

• Code generation. The Management client is generated from our OpenAPI spec. Keeping a hand-maintained authentication client bolted onto a generated management client was holding both back. Splitting them lets each evolve on its own terms.
• One authentication core, dogfooded. @auth0/auth0-auth-js is now the authentication engine behind auth0-nuxt, auth0-fastify, auth0-express, auth0-hono, auth0-react-router, and auth0-tanstackstart-react. We use it the same way you would.
• Faster feature adoption. Because every framework SDK now sits on that shared core, a new authentication feature has to land there first, which means it reaches all of those SDKs together. That was never the case with node-auth0's standalone authentication client.
• A more battle-tested auth layer. More SDKs on one core means more real-world usage hardening it.

📘 Migrating

• Migration guide: https://github.com/auth0/node-auth0/blob/master/v7_MIGRATION_GUIDE.md
• Using an AI agent? The Auth0 migration skill can perform most of the migration automatically: agent-skills/plugins/auth0/skills/auth0

⚠️v6 deprecation

Alongside this release, we're deprecating v6 (>=6.0.0 <7.0.0) on npm. You'll see a deprecation notice when installing it. To be explicit about what that does and doesn't mean:

• It's a signal to migrate, not a removal. v6 keeps working and stays installable.
• If you're on the Management API only, migrating to v7 is a straightforward version bump with no breaking changes.
• If you use the authentication client, follow the migration guide above to move to the new authentication SDKs.

Questions, migration snags, or anything that felt worse than v6 : reply here. We're watching this thread.