fix(nextjs): Adjust shared imports to remove edge runtime warnings #1924
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.
Description
Updates our
@clerk/shared
imports to remove some warnings about importing unsupported methods in certain runtimes. As part of this, I've also moved some utils out ofshared/utils
into their own dedicated files so that they can be imported on their own.isDevelopmentFromApiKey
has been moved toshared/keys
isProductionFromApiKey
has been moved toshared/keys
callWithRetry
into its top-level fileExample:
Note: This does not address the warnings that arise from
import { authMiddleware } from '@clerk/nextjs'
. This is a separate case that we'll need to handle differently.related to JS-599
Checklist
npm test
runs as expected.npm run build
runs as expected.Type of change
Packages affected
@clerk/clerk-js
@clerk/clerk-react
@clerk/nextjs
@clerk/remix
@clerk/types
@clerk/themes
@clerk/localizations
@clerk/clerk-expo
@clerk/backend
@clerk/clerk-sdk-node
@clerk/shared
@clerk/fastify
@clerk/chrome-extension
gatsby-plugin-clerk
build/tooling/chore