@clerk/upgrade 0.3.0 → 0.4.1

package/dist/versions/v5/common/new-localization-keys.md

@@ -1,134 +0,0 @@
----
-title: 'New localization keys added'
-matcher: "<ClerkProvider[\\s\\S]*?localization=[\\s\\S]*?>"
-matcherFlags: 'm'
-category: 'localization'
-warning: true
----
-
-As part of the redesign of Clerk's components, a number of new localization keys have been added and can be seen along with their default english values in the code block below. If you do not supply translated values for these keys in your custom localization, they will fall back to the default english values specified below.
-
-```js
-const newValues = {
-  formFieldLabel__organizationName: 'Name',
-  formFieldLabel__organizationSlug: 'Slug',
-  formFieldInputPlaceholder__emailAddresses: 'example@email.com, example2@email.com',
-  formFieldInputPlaceholder__organizationSlug: 'my-org',
-  signUp: {
-    start: {
-      subtitle: 'Welcome! Please fill in the details to get started.',
-      actionText: 'Already have an account?',
-    },
-    emailCode: {
-      subtitle: 'Enter the verification code sent to your email',
-    },
-    phoneCode: {
-      subtitle: 'Enter the verification code sent to your phone',
-    },
-    continue: {
-      subtitle: 'Please fill in the remaining details to continue.',
-      actionText: 'Already have an account?',
-    },
-  },
-  signIn: {
-    start: {
-      title: 'Sign in to {{applicationName}}',
-      subtitle: 'Welcome back! Please sign in to continue',
-      actionText: 'Don’t have an account?',
-    },
-    password: {
-      subtitle: 'Enter the password associated with your account',
-    },
-    forgotPasswordAlternativeMethods: {
-      label__alternativeMethods: 'Or, sign in with another method',
-    },
-    resetPassword: {
-      title: 'Set new password',
-    },
-    phoneCodeMfa: {
-      subtitle: 'To continue, please enter the verification code sent to your phone',
-    },
-    totpMfa: {
-      subtitle: 'To continue, please enter the verification code generated by your authenticator app',
-    },
-    backupCodeMfa: {
-      subtitle: 'Your backup code is the one you got when setting up two-step authentication.',
-    },
-  },
-  userProfile: {
-    formButtonPrimary__continue: 'Save',
-    start: {
-      headerTitle__account: 'Profile details',
-      profileSection: {
-        primaryButton: 'Edit profile',
-      },
-      emailAddressesSection: {
-        detailsAction__unverified: 'Verify',
-        destructiveAction: 'Remove email',
-      },
-      mfaSection: {
-        phoneCode: {
-          destructiveActionLabel: 'Remove',
-        },
-        backupCodes: {
-          actionLabel__regenerate: 'Regenerate',
-        },
-      },
-      dangerSection: {
-        title: 'Account termination',
-        deleteAccountButton: 'Delete account',
-      },
-    },
-    profilePage: {
-      imageFormSubtitle: 'Upload',
-      imageFormDestructiveActionSubtitle: 'Remove',
-    },
-    phoneNumberPage: {
-      title: 'Add a phone number',
-      infoText:
-        'A text message containing a verification link will be sent to this phone number. Message and data rates may apply.',
-    },
-    connectedAccountPage: {
-      socialButtonsBlockButton: '{{provider|titleize}}',
-    },
-    mfaPhoneCodePage: {
-      subtitle__availablePhoneNumbers:
-        'Select an existing phone number to register for SMS code two-step verification or add a new one.',
-      subtitle__unavailablePhoneNumbers:
-        'There are no available phone numbers to register for SMS code two-step verification, please add a new one.',
-    },
-    deletePage: {
-      actionDescription: 'Type "Delete account" below to continue.',
-    },
-  },
-  organizationSwitcher: {
-    action__createOrganization: 'Create organization',
-    action__manageOrganization: 'Manage',
-  },
-  organizationProfile: {
-    profilePage: {
-      title: 'Update Profile',
-      dangerSection: {
-        title: 'Danger',
-        leaveOrganization: {
-          actionDescription: 'Type "{{organizationName}}" below to continue.',
-        },
-        deleteOrganization: {
-          actionDescription: 'Type "{{organizationName}}" below to continue.',
-        },
-      },
-    },
-    invitePage: {
-      title: 'Invite new members',
-      subtitle: 'Enter or paste one or more email addresses, separated by spaces or commas.',
-    },
-  },
-  createOrganization: {
-    title: 'Create organization',
-  },
-  organizationList: {
-    title: 'Choose an account',
-    titleWithoutPersonal: 'Choose an organization',
-  },
-};
-```

package/dist/versions/v5/common/user-getorganizationinvitations-arguments-chanaged.md

@@ -1,16 +0,0 @@
----
-title: '`User.getOrganizationInvitations` arguments changed'
-matcher: "\\.getOrganizationInvitations\\("
-category: 'pagination-args'
----
-
-There have been a couple changes to the pagination arguments that can be passed into this function - `limit` has been renamed to `pageSize`, and `offset` has been renamed to `initialPage`. This will help to make it more clear and simple to reason about pagination control. Example of how changes might look below:
-
-```diff
-  const { data } = await user.getOrganizationInvitations({
--   limit: 10,
-+   pageSize: 10,
--   offset: 10,
-+   initialPage: 2,
-  })
-```

package/dist/versions/v5/common/user-getorganizationmemberships-arguments-chanaged.md

@@ -1,16 +0,0 @@
----
-title: '`User.getOrganizationMemberships` arguments changed'
-matcher: "\\.getOrganizationMemberships\\("
-category: 'pagination-args'
----
-
-There have been a couple changes to the pagination arguments that can be passed into this function - `limit` has been renamed to `pageSize`, and `offset` has been renamed to `initialPage`. This will help to make it more clear and simple to reason about pagination control. Example of how changes might look below:
-
-```diff
-  const { data } = await user.getOrganizationMemberships({
--   limit: 10,
-+   pageSize: 10,
--   offset: 10,
-+   initialPage: 2,
-  })
-```

package/dist/versions/v5/common/user-getorganizationsuggestions-arguments-chanaged.md

@@ -1,16 +0,0 @@
----
-title: '`User.getOrganizationSuggestions` arguments changed'
-matcher: "\\.getOrganizationSuggestions\\("
-category: 'pagination-args'
----
-
-There have been a couple changes to the pagination arguments that can be passed into this function - `limit` has been renamed to `pageSize`, and `offset` has been renamed to `initialPage`. This will help to make it more clear and simple to reason about pagination control. Example of how changes might look below:
-
-```diff
-  const { data } = await user.getOrganizationSuggestions({
--   limit: 10,
-+   pageSize: 10,
--   offset: 10,
-+   initialPage: 2,
-  })
-```

package/dist/versions/v5/js/external-account-avatarurl.md

@@ -1,7 +0,0 @@
----
-title: '`ExternalAccount.avatarUrl` -> `ExternalAccount.imageUrl`'
-matcher: "\\.avatarUrl"
-replaceWithString: '.imageUrl'
----
-
-The `avatarUrl` property of any [`ExternalAcccount` object](https://clerk.com/docs/references/javascript/external-account) has been changed to `imageUrl`.

package/dist/versions/v5/js/organization-create-string.md

@@ -1,12 +0,0 @@
----
-title: "`Organization.create('x')` -> `Organization.create({ name: 'x' })`"
-matcher: "Organization\\.create\\(\\s*[\"']"
-matcherFlags: 'm'
----
-
-Passing a string as an argument to `Organization.create` is no longer possible - instead, pass an object with the `name` property.
-
-```diff
-- Organization.create('...');
-+ Organization.create({ name: '...' });
-```

package/dist/versions/v5/js/organization-getdomains-arguments-change.md

@@ -1,15 +0,0 @@
----
-title: '`Organization.getDomains` arguments changed'
-matcher: "\\.getDomains\\("
----
-
-There have been a couple changes to the pagination arguments that can be passed into this function - `limit` has been renamed to `pageSize`, and `offset` has been renamed to `initialPage`. This will help to make it more clear and simple to reason about pagination control. Example of how changes might look below:
-
-```diff
-  const { data } = await organization.getDomains({
--   limit: 10,
-+   pageSize: 10,
--   offset: 10,
-+   initialPage: 2,
-  })
-```

package/dist/versions/v5/js/organization-getinvitations-arguments-changed.md

@@ -1,15 +0,0 @@
----
-title: '`Organization.getInvitations` arguments changed'
-matcher: "\\.getInvitations\\("
----
-
-There have been a couple changes to the pagination arguments that can be passed into this function - `limit` has been renamed to `pageSize`, and `offset` has been renamed to `initialPage`. This will help to make it more clear and simple to reason about pagination control. Example of how changes might look below:
-
-```diff
-  const { data } = await organization.getInvitations({
--   limit: 10,
-+   pageSize: 10,
--   offset: 10,
-+   initialPage: 2,
-  })
-```

package/dist/versions/v5/js/organization-getmembershiprequests-arguments-changed.md

@@ -1,15 +0,0 @@
----
-title: '`Organization.getMembershipRequests` arguments changed'
-matcher: "\\.getMembershipRequests\\("
----
-
-There have been a couple changes to the pagination arguments that can be passed into this function - `limit` has been renamed to `pageSize`, and `offset` has been renamed to `initialPage`. This will help to make it more clear and simple to reason about pagination control. Example of how changes might look below:
-
-```diff
-  const { data } = await organization.getMembershipRequests({
--   limit: 10,
-+   pageSize: 10,
--   offset: 10,
-+   initialPage: 2,
-  })
-```

package/dist/versions/v5/js/organization-getmemberships-arguments-changed.md

@@ -1,15 +0,0 @@
----
-title: '`Organization.getMemberships` arguments changed'
-matcher: "\\.getMemberships\\("
----
-
-There have been a couple changes to the pagination arguments that can be passed into this function - `limit` has been renamed to `pageSize`, and `offset` has been renamed to `initialPage`. This will help to make it more clear and simple to reason about pagination control. Example of how changes might look below:
-
-```diff
-  const { data } = await organization.getMemberships({
--   limit: 10,
-+   pageSize: 10,
--   offset: 10,
-+   initialPage: 2,
-  })
-```

package/dist/versions/v5/js/organization-getpendinginvitations.md

@@ -1,11 +0,0 @@
----
-title: "`Organization.getPendingInvitations()` -> `Organization.getInvitations({ status: 'pending' })`"
-matcher: "\\.getPendingInvitations\\("
----
-
-The `Organization.getPendingInvitations()` method has been removed. You can use `Organization.getInvitations` instead.
-
-```diff
-- Organization.getPendingInvitations();
-+ Organization.getInvitations({ status: 'pending' });
-```

package/dist/versions/v5/js/organization-getroles-arguments-changed.md

@@ -1,15 +0,0 @@
----
-title: '`Organization.getRoles` arguments changed'
-matcher: "\\.getRoles\\("
----
-
-There have been a couple changes to the pagination arguments that can be passed into this function - `limit` has been renamed to `pageSize`, and `offset` has been renamed to `initialPage`. This will help to make it more clear and simple to reason about pagination control. Example of how changes might look below:
-
-```diff
-  const { data } = await organization.getRoles({
--   limit: 10,
-+   pageSize: 10,
--   offset: 10,
-+   initialPage: 2,
-  })
-```

package/dist/versions/v5/js/organization-logourl.md

@@ -1,7 +0,0 @@
----
-title: '`Organization.logoUrl` -> `Organization.imageUrl`'
-matcher: "\\.logoUrl"
-replaceWithString: '.imageUrl'
----
-
-The `logoUrl` property of any [`Organization` object](https://clerk.com/docs/references/javascript/organization/organization#organization) has been changed to `imageUrl`.

package/dist/versions/v5/js/router-navigate-push-replace.md

@@ -1,18 +0,0 @@
----
-title: '`navigate` argument to `Clerk.load` replaced by `routerPush` and `routerReplace`'
-matcher: "Clerk\\.load\\([\\s\\S]*?navigate:[\\s\\S]*?\\)"
-matcherFlags: 'm'
----
-
-The `navigate` option allowed developers to override the default navigation behavior with a custom function. However, navigate was only able to push, not replace routes. We have now added the capability for the router to push or replace, and as such, updated `Clerk.load` so that it can handle either depending on the circumstance.
-
-Two new arguments have been added to options that can be passed to `Clerk.load` that replace the single `navigate` argument, and can be used to override the default navigation behavior for either a push or replace navigation. For more information on what push and replace mean in relation to the browser history api, [check out these wonderful MDN docs](https://developer.mozilla.org/en-US/docs/Web/API/History_API/Working_with_the_History_API).
-
-If you’d like to keep the same behavior as you had with the single `navigate` argument, pass the exact same function to as both the `routerPush` and `routerReplace` arguments and the behavior will be identical. For example:
-
-```diff
-- Clerk.load({ navigate: x => x })
-+ Clerk.load({ routerPush: x => x, routerReplace: x => x })
-```
-
-However, you now have the option to differentiate behavior based on whether the navigation will be a push or replace.

package/dist/versions/v5/js/user-getorganizationinvitations-arguments-chanaged.md

@@ -1,15 +0,0 @@
----
-title: '`User.getOrganizationInvitations` arguments changed'
-matcher: "\\.getOrganizationInvitations\\("
----
-
-There have been a couple changes to the pagination arguments that can be passed into this function - `limit` has been renamed to `pageSize`, and `offset` has been renamed to `initialPage`. This will help to make it more clear and simple to reason about pagination control. Example of how changes might look below:
-
-```diff
-  const { data } = await user.getOrganizationInvitations({
--   limit: 10,
-+   pageSize: 10,
--   offset: 10,
-+   initialPage: 2,
-  })
-```

package/dist/versions/v5/js/user-getorganizationmemberships-arguments-chanaged.md

@@ -1,15 +0,0 @@
----
-title: '`User.getOrganizationMemberships` arguments changed'
-matcher: "\\.getOrganizationMemberships\\("
----
-
-There have been a couple changes to the pagination arguments that can be passed into this function - `limit` has been renamed to `pageSize`, and `offset` has been renamed to `initialPage`. This will help to make it more clear and simple to reason about pagination control. Example of how changes might look below:
-
-```diff
-  const { data } = await user.getOrganizationMemberships({
--   limit: 10,
-+   pageSize: 10,
--   offset: 10,
-+   initialPage: 2,
-  })
-```

package/dist/versions/v5/js/user-getorganizationsuggestions-arguments-chanaged.md

@@ -1,15 +0,0 @@
----
-title: '`User.getOrganizationSuggestions` arguments changed'
-matcher: "\\.getOrganizationSuggestions\\("
----
-
-There have been a couple changes to the pagination arguments that can be passed into this function - `limit` has been renamed to `pageSize`, and `offset` has been renamed to `initialPage`. This will help to make it more clear and simple to reason about pagination control. Example of how changes might look below:
-
-```diff
-  const { data } = await user.getOrganizationSuggestions({
--   limit: 10,
-+   pageSize: 10,
--   offset: 10,
-+   initialPage: 2,
-  })
-```

package/dist/versions/v5/js/user-update-password.md

@@ -1,18 +0,0 @@
----
-title: "`User.update({ password: 'x' })` -> `User.updatePassword('x')`"
-matcher: "\\.update\\([\\s\\S]*?password:[\\s\\S]*?\\)"
-category: 'deprecation-removal'
-matcherFlags: 'm'
----
-
-If you are updating a user's password via the [`User.update` method](https://clerk.com/docs/references/javascript/user/user#update), it must be changed to [`User.updatePassword`](https://clerk.com/docs/references/javascript/user/password-management#update-password) instead. This method will require the current password as well as the desired new password. We made this update to improve the security of password changes. Example below:
-
-```diff
-- user.update({ password: 'foo' });
-
-+ user.updatePassword({
-+   currentPassword: 'bar',
-+   newPassword: 'foo',
-+   signOutOfOtherSessions: true,
-+ });
-```

package/dist/versions/v5/next/ismetamaskerror-import-change.md

@@ -1,14 +0,0 @@
----
-title: '`isMetamaskError` import moved under `/errors`'
-matcher: "import\\s+{[\\s\\S]*?isMetamaskError[\\s\\S]*?from\\s+['\"]@clerk\\/(nextjs)[\\s\\S]*?['\"]"
-matcherFlags: 'm'
-category: 'top-level-imports'
-replaceWithString: 'nextjs/errors'
----
-
-The `isMetamaskError` import path has changed from `@clerk/nextjs` to `@clerk/nextjs/errors`. You must update your import path in order for it to work correctly. Example below of the fix that needs to be made:
-
-```diff
-- import { isMetamaskError } from "@clerk/nextjs"
-+ import { isMetamaskError } from "@clerk/nextjs/errors"
-```

package/dist/versions/v5/next/redirecttosignin-removed.md

@@ -1,6 +0,0 @@
----
-title: '`redirectToSignIn` import removed'
-matcher: "import\\s+{[\\s\\S]*?[,\\s]redirectToSignIn[,\\s][\\s\\S]*?from\\s+['\"]@clerk\\/nextjs[\\s\\S]*?['\"]"
----
-
-We have removed the top level `redirectToSignIn` import, because X. Instead, you can use Y.

package/dist/versions/v5/next/redirecttosignup-removed.md

@@ -1,6 +0,0 @@
----
-title: '`redirectToSignUp` import removed'
-matcher: "import\\s+{[\\s\\S]*?[,\\s]redirectToSignUp[,\\s][\\s\\S]*?from\\s+['\"]@clerk\\/nextjs[\\s\\S]*?['\"]"
----
-
-We have removed the top level `redirectToSignUp` import, because X. Instead, you can use Y.

package/dist/versions/v5/next/with-clerk-middleware-removed.md

@@ -1,11 +0,0 @@
----
-title: '`withClerkMiddleware` removed'
-category: 'middleware'
-matcher: "withClerkMiddleware\\("
----
-
-`withClerkMiddleware` has been deprecated and is now removed in v5. We recommend moving to `clerkMiddleware` instead. Here’s an example of how the code would look before and after:
-
-```js
-// TODO
-```

package/dist/versions/v5/nextjs/api-url-value-change.md

@@ -1,8 +0,0 @@
----
-title: '`API_URL` value has changed'
-matcher: "API_URL[\\s\\S]+?from\\s+['\"]@clerk\\/nextjs\\/server['\"]"
-matcherFlags: 'm'
-warning: true
----
-
-The value of this export has changed from `https://api.clerk.dev` to `https://api.clerk.com`. If you were relying on the text content of this value not changing, you may need to make adjustments.

package/dist/versions/v5/nextjs/auth-import-change.md

@@ -1,14 +0,0 @@
----
-title: '`auth` import moved under `/server`'
-matcher: "import\\s+{[\\s\\S]*?[,\\s]auth[,\\s][\\s\\S]*?from\\s+['\"]@clerk\\/(nextjs)[\\s\\S]*?['\"]"
-matcherFlags: 'm'
-category: 'top-level-imports'
-replaceWithString: 'nextjs/server'
----
-
-The `auth` import path has changed from `@clerk/nextjs` to `@clerk/nextjs/server`, as this is a helper that should be only used on the server side. You must update your import path in order for it to work correctly. Example below of the fix that needs to be made:
-
-```diff
-- import { auth } from "@clerk/nextjs"
-+ import { auth } from "@clerk/nextjs/server"
-```

package/dist/versions/v5/nextjs/auth-middleware-deprecated.md

@@ -1,50 +0,0 @@
----
-title: '`authMiddleware` deprecated'
-matcher: "import\\s+{[\\s\\S]*?authMiddleware[\\s\\S]*?}\\s+from\\s+['\"]@clerk\\/nextjs[\\s\\S]*?['\"]"
-category: 'middleware'
-matcherFlags: 'm'
-warning: true
----
-
-The [`authMiddleware`](https://clerk.com/docs/references/nextjs/auth-middleware) API from `@clerk/nextjs` has been marked as deprecated. We highly recommend using [`clerkMiddleware`](https://clerk.com/docs/references/nextjs/clerk-middleware) going forward. `clerkMiddleware` protects no routes by default and you need to add your individual routes you want to opt into protection. Here's an example of having all routes public except for everything under `/dashboard`.
-
-For more documentation on the new `clerkMiddleware` function, check out [our official docs](https://clerk.com/docs/references/nextjs/clerk-middleware)!
-
-**Before:**
-
-```ts
-// middleware.ts
-
-import { authMiddleware } from '@clerk/nextjs';
-
-export default authMiddleware({
-  publicRoutes: req => !req.url.includes('/dashboard'),
-});
-
-export const config = {
-  matcher: ['/((?!.+\\.[\\w]+$|_next)._)', '/', '/(api|trpc)(._)'],
-};
-```
-
-**After:**
-
-```ts
-// middleware.ts
-
-import { clerkMiddleware, createRouteMatcher } from '@clerk/nextjs/server';
-import { NextResponse } from 'next/server';
-
-const isProtectedRoute = createRouteMatcher(['/dashboard(.*)']);
-
-export default clerkMiddleware((auth, request) => {
-  if (isProtectedRoute(request)) {
-    auth().protect();
-  }
-
-  return NextResponse.next();
-});
-
-export const config = {
-  matcher: ['/((?!.+\\.[\\w]+$|_next)._)', '/', '/(api|trpc)(._)'],
-};
-```

package/dist/versions/v5/nextjs/authmiddleware-apikey.md

@@ -1,15 +0,0 @@
----
-title: '`apiKey` -> `secretKey` as param to `authMiddleware`'
-matcher: "authMiddleware\\({[\\s\\S]*?apiKey:[\\s\\S]*?}\\)"
-category: 'deprecation-removal'
-matcherFlags: 'm'
----
-
-The `apiKey` argument passed to `authMiddleware` must be changed to `secretKey`.
-
-```diff
-import { authMiddleware } from '@clerk/nextjs';
-
-- authMiddleware({ apiKey: '...' });
-+ authMiddleware({ secretKey: '...' });
-```

package/dist/versions/v5/nextjs/authmiddleware-frontendapi.md

@@ -1,15 +0,0 @@
----
-title: '`frontendApi` -> `publishableKey` as param to `authMiddleware`'
-matcher: "authMiddleware\\({[\\s\\S]*?frontendApi:[\\s\\S]*?}\\)"
-category: 'deprecation-removal'
-matcherFlags: 'm'
----
-
-The `frontendApi` argument passed to `authMiddleware` must be changed to `publishableKey`
-
-```diff
-import { authMiddleware } from "@clerk/nextjs/server"
-
-- authMiddleware({ frontendApi: '...' })
-+ authMiddleware({ publishableKey: '...' })
-```

package/dist/versions/v5/nextjs/authmiddleware-import-change.md

@@ -1,14 +0,0 @@
----
-title: '`authMiddleware` import moved under `/server`'
-matcher: "import\\s+{[\\s\\S]*?authMiddleware[\\s\\S]*?from\\s+['\"]@clerk\\/(nextjs)[\\s\\S]*?['\"]"
-matcherFlags: 'm'
-category: 'top-level-imports'
-replaceWithString: 'nextjs/server'
----
-
-The `authMiddleware` import path has changed from `@clerk/nextjs` to `@clerk/nextjs/server`, as this is a helper that should be only used on the server side. You must update your import path in order for it to work correctly. Note as well that `authMiddleware` is deprecated as of this release, and we recommend [using `clerkMiddleware` instead](https://clerk.com/docs/references/nextjs/clerk-middleware). Example below of the fix that needs to be made:
-
-```diff
-- import { authMiddleware } from "@clerk/nextjs"
-+ import { authMiddleware } from "@clerk/nextjs/server"
-```

package/dist/versions/v5/nextjs/buildclerkprops-import-change.md

@@ -1,14 +0,0 @@
----
-title: '`buildClerkProps` import moved under `/server`'
-matcher: "import\\s+{[\\s\\S]*?buildClerkProps[\\s\\S]*?from\\s+['\"]@clerk\\/(nextjs)[\\s\\S]*?['\"]"
-matcherFlags: 'm'
-category: 'top-level-imports'
-replaceWithString: 'nextjs/server'
----
-
-The `buildClerkProps` import path has changed from `@clerk/nextjs` to `@clerk/nextjs/server`, as this is a helper that should be only used on the server side. You must update your import path in order for it to work correctly. Example below of the fix that needs to be made:
-
-```diff
-- import { buildClerkProps } from "@clerk/nextjs"
-+ import { buildClerkProps } from "@clerk/nextjs/server"
-```

package/dist/versions/v5/nextjs/clerk-import-change.md

@@ -1,13 +0,0 @@
----
-title: '`Clerk` import moved under `/server`'
-matcher: "import\\s+{[\\s\\S]*?[,\\s]Clerk[,\\s][\\s\\S]*?from\\s+['\"]@clerk\\/nextjs[\\s\\S]*?['\"]"
-category: 'top-level-imports'
-matcherFlags: 'm'
----
-
-The `Clerk` import path has changed from `@clerk/nextjs` to `@clerk/nextjs/server`, as this is a helper that should be only used on the server side. You must update your import path in order for it to work correctly. Note as well that the `Clerk` export has changed to `createClerkClient` as part of the v5 changes. Example below of the fix that needs to be made:
-
-```diff
-- import { Clerk } from "@clerk/nextjs"
-+ import { createClerkClient } from "@clerk/nextjs/server"
-```

package/dist/versions/v5/nextjs/clerk-js-version-next-public.md

@@ -1,9 +0,0 @@
----
-title: '`CLERK_JS_VERSION` should be `NEXT_PUBLIC_CLERK_JS_VERSION`'
-category: 'deprecation-removal'
-matcher: '^[^_]*CLERK_JS_VERSION'
----
-
-If you are using `CLERK_JS_VERSION` as an environment variable, it should be changed to `NEXT_PUBLIC_CLERK_JS_VERSION` instead.
-
-This change brings our SDK up to date with the latest standards for next.js - that public environment variables should have the `NEXT_PUBLIC_` prefix. This env variable is not private, so it should get the public prefix.

package/dist/versions/v5/nextjs/constants-import-change.md

@@ -1,14 +0,0 @@
----
-title: '`constants` import moved under `/server`'
-matcher: "import\\s+{[\\s\\S]*?constants[\\s\\S]*?from\\s+['\"]@clerk\\/(nextjs)[\\s\\S]*?['\"]"
-matcherFlags: 'm'
-category: 'top-level-imports'
-replaceWithString: 'nextjs/server'
----
-
-The `constants` import path has changed from `@clerk/nextjs` to `@clerk/nextjs/server`, as this is a helper that should be only used on the server side. You must update your import path in order for it to work correctly. Example below of the fix that needs to be made:
-
-```diff
-- import { constants } from "@clerk/nextjs"
-+ import { constants } from "@clerk/nextjs/server"
-```

package/dist/versions/v5/nextjs/createauthenticaterequest-import-change.md

@@ -1,14 +0,0 @@
----
-title: '`createAuthenticateRequest` import moved under `/server`'
-matcher: "import\\s+{[\\s\\S]*?createAuthenticateRequest[\\s\\S]*?from\\s+['\"]@clerk\\/(nextjs)[\\s\\S]*?['\"]"
-matcherFlags: 'm'
-category: 'top-level-imports'
-replaceWithString: 'nextjs/server'
----
-
-The `createAuthenticateRequest` import path has changed from `@clerk/nextjs` to `@clerk/nextjs/server`, as this is a helper that should be only used on the server side. You must update your import path in order for it to work correctly. Example below of the fix that needs to be made:
-
-```diff
-- import { createAuthenticateRequest } from "@clerk/nextjs"
-+ import { createAuthenticateRequest } from "@clerk/nextjs/server"
-```