Hello, There is often confusion in CodeEvolution training…
1 reactions
Hello,
There is often confusion in CodeEvolution training or other Next.js tutorials: it is usually not Clerk that is deprecated, but some older Clerk APIs that are.
For example, Clerk has replaced several elements over the versions:
authMiddleware() → replaced by clerkMiddleware()
frontendApi → replaced by publishableKey
Some synchronous methods like auth() or clerkClient() have become asynchronous in recent versions in order to follow the evolution of Next.js.
In fact, Clerk continues to be actively maintained. The package@clerk/nextjs is always released and updated for recent versions of Next.js.
Why would a formation say it is “deprecated”?
The training may have been recorded with an older version of Next.js or Clerk.
The trainer is talking about an old method (authMiddleware) and not the Clerk service itself.
Some trainers today prefer to recommend NextAuth/Auth.js, which is very popular in the Next.js ecosystem, but that doesn't mean Clerk is abandoned.
In 2026, Clerk remains a completely valid solution for authentication with Next.js, especially if you want a quick setup with ready-to-use user management.
There is often confusion in CodeEvolution training or other Next.js tutorials: it is usually not Clerk that is deprecated, but some older Clerk APIs that are.
For example, Clerk has replaced several elements over the versions:
authMiddleware() → replaced by clerkMiddleware()
frontendApi → replaced by publishableKey
Some synchronous methods like auth() or clerkClient() have become asynchronous in recent versions in order to follow the evolution of Next.js.
In fact, Clerk continues to be actively maintained. The package@clerk/nextjs is always released and updated for recent versions of Next.js.
Why would a formation say it is “deprecated”?
The training may have been recorded with an older version of Next.js or Clerk.
The trainer is talking about an old method (authMiddleware) and not the Clerk service itself.
Some trainers today prefer to recommend NextAuth/Auth.js, which is very popular in the Next.js ecosystem, but that doesn't mean Clerk is abandoned.
In 2026, Clerk remains a completely valid solution for authentication with Next.js, especially if you want a quick setup with ready-to-use user management.
| 36,000 mlx | |
| 47 | |
| 1 |
comments
Actually only the old APIs got deprecated, not
1