Skip to main content

Release 0.1.124

The target-stack preview no longer shows your app through a rewriting proxy. It now runs a real browser on the server, beside the app, and streams the picture to you — so the screens you review are the screens the app actually serves.

Upgrade notes​

  • One database migration, applied automatically on upgrade.
  • No changes to docker-compose.yml.
  • A prototype branch that had node_modules committed to it is repaired on the next prototype job. Nothing to do by hand.

Changes​

The preview runs a real browser instead of a proxied frame. Previously the preview loaded your app through a proxy that rewrote URLs, cookies and paths so it could be shown inside our page. That rewriting could not be made correct in general, and when it went wrong the screen looked broken for reasons that had nothing to do with your app: a sign-in that would not complete, a page that worked once and failed on reload, an API call to an address that only exists inside the container. The preview now opens the app in a browser that sits on the same network as the app itself, so nothing is rewritten and there is nothing left to go wrong in that layer.

Maximize, instead of a second tab. The preview fills the window in place. You stay on the feature, with its Gherkin and its build controls, and the app is laid out at the larger width rather than scaled up. Adjust is available while maximized, docked beside the app, and a half-written comment survives maximizing and restoring.

The preview has the app's own controls. Back, forward, reload, and an address you can type into — so you can reach a screen the app does not link to, and see which screen you are on. The route updates as you navigate.

Picking an element highlights it. With Pick on, the element under your pointer is outlined before you click, and the one you picked stays outlined while you write about it. Your app's own hover styles work for the same reason.

The preview is faster. Scrolling and interaction were slow enough to be distracting. Three separate causes were fixed; the largest was that each frame was being held up by the previous one having to finish its journey to your browser.

Prototype jobs no longer die on a branch that tracks node_modules. On an affected project every prototype job failed, with a message about a file that could not be removed, and an update banner that never cleared. Those branches repair themselves on the next job, and new ones cannot get into that state.

Documentation is published at docs.repave.ai. Versioned, and the same pages are available inside the product.

Repave IDE session costs appear on the cost pages, grouped by feature, so an IDE session's spend is attributed like any other work.

Fixes​

  • A repository that cannot be pulled now says why, instead of reporting "nothing to pull".
  • A refused branch states what its foreign commits would change.
  • Recovering a split replay works when the base branch has moved on.
  • The non-functional Help button has been removed from the header.