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.
Don't dispose previous pages in dev mode
See original GitHub issueIn dev mode, when navigating from e.g index page to page B, it will then after a while destroy the index page: Disposing inactive page(s): /. Why not keeping it in memory, at least as long as there aren’t too many pages built?
Rather than disposing on timeout, it appears better to me to dispose pages when there are too many of them in memory.
This would allow to then have fast client-side transitions (after the first load), which allows to have a feel of these transitions without needing to deploy to prod.
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@kunokdev it’s configurable now in v4 beta https://github.com/zeit/next.js#configuring-the-ondemandentries
“too many pages” is kind a hard to decide. What we can do is to provide an option on asking how many pages to buffer in the memory.
I like that and we can default that to 2.