Open
Conversation
next/compat/router shimnext/compat/router shim
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a new
compat-routershim fornext/compat/router, the public Next.js API intended for components shared between Pages Router and App Router.@clerk/nextjs(ref) import fromnext/compat/router. Thenext/compat/routerpackage entry is CJS (module.exports = require(...)), which Vite cannot extract named ESM exports from — causing a "does not provide an export named 'useRouter'" error at runtime. Adding a native ESM shim in vinext resolves this without requiring apps to add aresolve.aliasworkaround.Temporary fix:
Locally tested via
pnpm link