gatsby: [V2] Reach/router extremely slow while `gatsby develop`

Context

All dependencies up-to-date.

I just migrated from react-dom-router to reach/router (following these instructions), and I’m encountering a strange behaviour:

Everything works as expected on a build project
Every route change while gatsby develop is totally buggy: the current page blink, then change after a huge amount of time.

Did any of you encounter that bug? Any idea?

I also started experiencing this,

Here’s the performance profile gatsby-slow-link.zip

There is a 5 second lag before the page switch occurs. The url is updated instantly.

The original issue was fixed. Please open a new issue with reproduction instructions for what you’re seeing now.

@JoaoTMDias in regard to

Last night I tried to follow the guide from upgrading from v1 to v2 and had all sorts of issues.

Was there information missing from the guide? Or were things unclear? Would love to get your feedback to see if I could make it better! 🙏

I can confirm this issue also.

The activeClassName also gets passed:

<a aria-current="page" location="[object Object]" activeclassname="active" class="active" href="/contact">Contact</a>