Ado Kukic

@philipheinser nope. I removed all functionality from the components to try to isolate the issue. The components don't do anything other than return a message. The only difference is that...

I also recreated the repo on stackblitz (https://stackblitz.com/edit/vercel-next-js-p1gsmj?file=next.config.js,app%2Fpage.tsx,app%2Flayout.tsx,app%2F[post]%2Fpage.tsx,app%2F[post]%2F[comment]%2Fpage.tsx) and am not able to reproduce the issue there. I wonder if this is perhaps Windows related?

This is a common problem if you are trying to use the minified version of the router library. Try switching to the non-minified version and the problem should go away.

@dieuhd - have you also updated the other libraries including rxjs and zone (as well as devDependencies). I had that issue arise during the bump to beta 9 - but...