<Link> should be able to navigate to dynamic API routes

[scerelli]

What version of Next.js are you using?

11.1.2

What version of Node.js are you using?

v15.14.0

What browser are you using?

Firefox, Chrome

What operating system are you using?

macOS

How are you deploying your application?

Vercel

Describe the Bug

I'm using auth0 integration with next.js that generates some endpoints in the NextJS API layer to which i navigate from the front end when I have to perform auth stuff like log in, logout etc

so I have /api/auth/login /api/auth/logout automatically generated by @auth0/nextjs-auth0

What happen:
if I use a simple <a> tag everything works just fine but of course ESLint sees it as an internal page, so it fails passing the checks because it suggests me to use <Link> instead of an <a> (https://nextjs.org/docs/messages/no-html-link-for-pages)

If I use <Link> i get an error:
Uncaught (in promise) Error: Failed to load script: /_next/static/chunks/pages/api/auth/%5B...auth0%5D.js because it is not a page. `

Expected Behavior

I expect to be able to navigate also to api routes.

Or

I expect the error documentation to have some information regarding this scenario.

To Reproduce

• Create a new next project
• Create a dynamic api route that creates several endpoints, each endpoint redirects you somewhere export it like pages/api/[...something].js
• Try to link to the an api route just created, using the <Link> components

[vitormv]

Having the same issue. Since the v11.1.0 where the locale part of the url was removed. But also, erroneously, the component STILL appends the locale, which it shouldnt, because of #26629

Also, appending <Link locale={false} (...) does not solve the issue either, still get the

 Uncaught (in promise) Error: Failed to load script: /_next/static/chunks/pages/api/auth/%5B...auth0%5D.js because it is not a page. `

v11.1.0 was a MAJOR breaking change, I wish there was a bigger announcement about it. It completely breaks any page that links to an API route, and currently I do not know how to get around that.

[scerelli]

@vitormv for the future. Try to avoid using third party components/libraries directly in your app.

You should try to always wrap the parts of the code you don't own (like this Link) inside your own components, api, so on every breaking change you would not have this kind of issues.

for example create your own Link component that exports the next.js link component like:

export MyLink = ({ href, children }) => {
  const isApi = href.split('/').includes('api'); //this is just to make you understand but this is too fragile you should use regex

  if(isApi) {
    return (
      <a href={href}>{children}</a>
    )
  }

  return (
    <Link href={href}>
      {children}
    </Link>
  )
}

i didn't try this, so it may not work, but you get the idea.

[hkogge]

This issue also applies to redirects.

When using a redirect in next.config.js

async redirects() {
    return [
      {
        source: '/foo',
        destination: '/bar',
        permanent: false,
      },
    ];
},

and then using a page link

<Link href="/foo">
   <a>Should redirect to /bar</a>
</Link>

Will lead to the error from OP and a 404 instead of redirecting to /bar.

edit: for the record, we are still on 11.1.3 so I don't know if the issue was fixed in later versions.

[github-actions]

Please verify that your issue can be recreated with next@canary.

Why was this issue marked with the please verify canary label?

We noticed the provided reproduction was using an older version of Next.js, instead of canary.

The canary version of Next.js ships daily and includes all features and fixes that have not been released to the stable version yet. You can think of canary as a public beta. Some issues may already be fixed in the canary version, so please verify that your issue reproduces by running npm install next@canary and test it in your project, using your reproduction steps.

If the issue does not reproduce with the canary version, then it has already been fixed and this issue can be closed.

How can I quickly verify if my issue has been fixed in canary?

The safest way is to install next@canary in your project and test it, but you can also search through closed Next.js issues for duplicates or check the Next.js releases. You can also use the GitHub template (preferred), or the CodeSandbox or StackBlitz templates to create a reproduction with canary from scratch.

My issue has been open for a long time, why do I need to verify canary now?

Next.js does not backport bug fixes to older versions of Next.js. Instead, we are trying to introduce only a minimal amount of breaking changes between major releases.

What happens if I don't verify against the canary version of Next.js?

An issue with the please verify canary that receives no meaningful activity (e.g. new comments that acknowledge verification against canary) will be automatically closed and locked after 30 days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue, with the required reproduction, using next@canary.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps. Furthermore, you can upvote the issue using the 👍 reaction on the topmost comment (please do not comment "I have the same issue" without repro steps). Then, we can sort issues by votes to prioritize.

I think my reproduction is good enough, why aren't you looking into it quicker?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

• How to Contribute to Open Source (Next.js)
• How to create a Minimal, Complete, and Verifiable example
• Reporting a Next.js bug
• Next.js Triaging issues

[balazsorban44]

This issue has been automatically closed because it wasn't verified against next@canary. If you think it was closed by accident, please leave a comment. If you are running into a similar issue, please open a new issue with a reproduction. Thank you.

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.