Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Conflict with NextJS Link Component as Prop

See original GitHub issue

As of next@9 nextjs Link also accepts as prop for dynamic routing so it breaks dynamic routed links, I am happy to submit PR fix for chakra-ui but will it be possible for chakra-ui’s Link component as prop to be renamed to something else?

Reference

https://github.com/zeit/next.js#dynamic-routing

Issue Analytics

State:
Created 4 years ago
Comments:10 (4 by maintainers)

Top GitHub Comments

34reactions

segunadebayocommented, Oct 1, 2019

Hi @harshzalavadiya,

How about you try this

import NextLink from "@next/link"
import { Link } from "@chakra-ui/core"

 <NextLink href="/post/[pid]" as={`/post/${pid}`}>
      <Link>Post {pid}</Link>
 </NextLink>

Since nextjs link is a default export, you can rename it to NextLink so there’s no conflict. Changing Chakra’s Link component name will cause some breaking change.

13reactions

geemanjscommented, Apr 18, 2021

Hey - Heres a TS example 👍

Definition: https://github.com/chakra-ui/chakra-ui/blob/develop/examples/nextjs-typescript/components/NextChakraLink.tsx

Usage: https://github.com/chakra-ui/chakra-ui/blob/develop/examples/nextjs-typescript/pages/properties/index.tsx#L12

Broken links - see https://github.com/chakra-ui/chakra-ui/issues/132#issuecomment-821944201