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.

Trailing slash route mismatch

See original GitHub issue

Hey guys, I think this is still an issue. When using trailingSlash: true and basePath: /dev you get warnings on the console like so: Warning: Prop 'href' did not match. Server: "/dev/second" Client: "/dev/second/".

Tried both ways:

<Link href="/second">
  <a>Second Page</a>
</Link>

and

<Link href="/second/">
  <a>Second Page</a>
</Link>

next version 9.4.5-canary.42

@Unsfer @Timer

_Originally posted by @marlonmarcello in https://github.com/vercel/next.js/issues/15194#issuecomment-662167808_

Issue Analytics

State:
Created 3 years ago
Reactions:2
Comments:12 (9 by maintainers)

Top GitHub Comments

2reactions

awareness481commented, Jul 25, 2020

@awareness481 You are using the exportTrailingSlash and not the trailingSlash option. You’ll also need to use next@9.4.5-canary.43 until the next minor version. Which example were you trying to run?

Incidentally, I thought I thought I had to use exportTrailingSlash: true. I can’t reproduce using trailingSlash: true in the next.config.js

1reaction

timneutkenscommented, Jul 26, 2020

Sounds like this can be closed then because exportTrailingSlash is something different and should no longer be used when the trailingSlash option is on stable.