You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enhancement
At the moment it's extremely slow to run BTR in watch mode with a large amount of pages. This is due to us not being able to determine what to incrementally/partially render per build. It's unlikely it's ever going to be possible to determine what changed between a build and a page.
What we can do though, is take advantage of when in watch and serve mode we can conditionally render just the page that is being requested at the point of request. This would mean we would only render 1 page in BTR per page visited, effectively making the BTR part no cost during in development.
This will require some changes to the BTR plugin to be able to execute for just a single page, and completely decouple it from webpack. We can then write a small express middleware that runs BTR based on the request made.
The text was updated successfully, but these errors were encountered:
Enhancement
At the moment it's extremely slow to run BTR in watch mode with a large amount of pages. This is due to us not being able to determine what to incrementally/partially render per build. It's unlikely it's ever going to be possible to determine what changed between a build and a page.
What we can do though, is take advantage of when in watch and serve mode we can conditionally render just the page that is being requested at the point of request. This would mean we would only render 1 page in BTR per page visited, effectively making the BTR part no cost during in development.
This will require some changes to the BTR plugin to be able to execute for just a single page, and completely decouple it from webpack. We can then write a small express middleware that runs BTR based on the request made.
The text was updated successfully, but these errors were encountered: