-
Notifications
You must be signed in to change notification settings - Fork 462
chore(nextjs): Drop deprecations #2006
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
dfcb90b
chore(nextjs): Drop `app-beta` subpath import
dimkl 7393f7e
chore(nextjs): Drop `*MagicLink*` related exports
dimkl ced9d8d
chore(nextjs): Drop `NEXT_PUBLIC_CLERK_FRONTEND_API` and `frontendApi`
dimkl 0326799
chore(nextjs): Drop `ssr` subpath import
dimkl d9e999e
chore(nextjs): Drop `edge-middleware` subpath import
dimkl 0c36690
chore(nextjs): Drop `CLERK_JS_VERSION`
dimkl 08b9373
chore(nextjs): Drop `CLERK_API_KEY` and `apiKey`
dimkl 2d4612e
chore(nextjs): Refactor to use `isDevelopmentFromApiKey` from `@cler…
dimkl 6cfd6f6
chore(nextjs): Drop `withClerkMiddleware`
dimkl bda4364
chore(nextjs): Drop constants from exports
dimkl 4fe6c24
chore(nextjs): Drop `api` subpath import
dimkl d676661
chore(nextjs): Drop unused `@clerk/clerk-sdk-node` dependency
dimkl a47baa2
chore(nextjs): Add changeset
dimkl File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| --- | ||
| '@clerk/nextjs': major | ||
| --- | ||
|
|
||
| Drop deprecations. Migration steps: | ||
| - use `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY` instead of `NEXT_PUBLIC_CLERK_FRONTEND_API` env variable | ||
| - use `NEXT_PUBLIC_CLERK_JS_VERSION` instead of `CLERK_JS_VERSION` | ||
| - use `CLERK_SECRET_KEY` instead of `CLERK_API_KEY` | ||
| - use `publishableKey` instead of `frontendApi` | ||
| - use `isEmailLinkError` instead of `isMagicLinkError` | ||
| - use `EmailLinkErrorCode` instead of `MagicLinkErrorCode` | ||
| - use `useEmailLink` instead of `useMagicLink` | ||
| - use `@clerk/nextjs` instead of `@clerk/nextjs/app-beta` | ||
| - use `@clerk/nextjs` instead of `@clerk/nextjs/ssr` | ||
| - use `@clerk/nextjs` instead of `@clerk/nextjs/edge-middleware` or `@clerk/nextjs/edge-middlewarefiles` | ||
| - use `@clerk/nextjs` instead of `@clerk/nextjs/api` | ||
| - use middleware with `authMiddleware` instead of `withClerkMiddleware` | ||
| - avoid using exported constants: `API_URL`, `API_VERSION`, `CLERK_JS_URL`, `CLERK_JS_VERSION`, `DOMAIN`, `IS_SATELLITE`, `PROXY_URL`, `PUBLISHABLE_KEY`, `SECRET_KEY`, `SIGN_IN_URL`, `SIGN_UP_URL` | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dimkl Should we mark these as breaking?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought that the major version bump should indicate that but we can also mark them as breaking changes. All the changes with
majorversion are breaking. What do you think?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merging this to continue with the cleanup and i will update the changeset if we want to somehow mark the changes as breaking.