Absolutely. Next’s router kind of kneecapped a feature we were building out recently and we had to adjust our implementation accordingly. The router is so deep

Absolutely. Next’s router kind of kneecapped a feature we were building out recently and we had to adjust our implementation accordingly. The router is so deeply entwined with getServerSideProps - we couldn’t find a way, including using shallow transitions, to push to the same path without triggering rebuilding the page due to a request to next/_data which returned the corresponding server side props. Amongst other things. It’s a wonderful framework, there’s no question. The router is definitely not its strength though.