Prevent state from resetting when router.push causes a re-render in Next.js 13 app directory · vercel next.js · Discussion #48154 · GitHub
![javascript - Uncaught (in promise) TypeError: _this2.context.router.push is not a function - Stack Overflow javascript - Uncaught (in promise) TypeError: _this2.context.router.push is not a function - Stack Overflow](https://i.stack.imgur.com/VMpey.jpg)
javascript - Uncaught (in promise) TypeError: _this2.context.router.push is not a function - Stack Overflow
![reactjs - Error: useRoutes() may be used only in the context of a <Router> component - Stack Overflow reactjs - Error: useRoutes() may be used only in the context of a <Router> component - Stack Overflow](https://i.stack.imgur.com/66f9J.png)
reactjs - Error: useRoutes() may be used only in the context of a <Router> component - Stack Overflow
![router.push()` during setup leads to "Unhandled error during execution of scheduler flush." and then `node is null` · Issue #6034 · vuejs/core · GitHub router.push()` during setup leads to "Unhandled error during execution of scheduler flush." and then `node is null` · Issue #6034 · vuejs/core · GitHub](https://user-images.githubusercontent.com/16977446/171056148-eb295ab9-df7a-4ff4-b5d4-4b1563e881e9.png)
router.push()` during setup leads to "Unhandled error during execution of scheduler flush." and then `node is null` · Issue #6034 · vuejs/core · GitHub
![Andrea Bizzotto 💙 on Twitter: "When using GoRouter for declarative navigation, you'll often have to choose between: - GOING to a route - PUSHING a route What is the difference between the Andrea Bizzotto 💙 on Twitter: "When using GoRouter for declarative navigation, you'll often have to choose between: - GOING to a route - PUSHING a route What is the difference between the](https://pbs.twimg.com/media/FNbD-NmWQAQKJv_.png)