October 24th

This week we had 25 contributors and 30+ PRs.

@jselmani, @joel-bentley, @pradeepgangwar, @leibale, @jainsneha23, @bomsy, @nyrosmith, @stefanjudis, @rameramwe, @amelzer, @jasonLaster, @lukaszsobek, @tohmjudson, @michaelgv, @ahuth, @darkwing, @juliandescottes, @yurydelendik, @codehag, @wldcordeiro, @James300

Performance

Performance is one of our primary goals post launch. We’ve identified two bottlenecks, naive computations. @jselmani is helping us migrate to background SVGs. @jasonLaster is looking at deferring expensive work like calculating how variables are mapped when there is a bundle.

Frameworks

We landed call stack logs from the Next.js, nuxt, Aframe, and Marko projects. Also a special shout out to Next.js, which we’re now using to host our bots!

We also landed support for finding the classes and imports in a source file as well. We’re using this data to identify files that have a React component!

Frameworks
4476-0
4460-0
4458-0
4430-0

UI Polish

We’re continuing to get great UI polish and the product is looking better and better.

Footer
4474-0

Bug

Perhaps the single best thing about launching a product is the fantastic bugs that are filed. This week, @bomsy helped us solve two edge cases w/ highlighting the first line of a file when the debugger pausing and previewing computed properties, e.g. the a variable in this example {[a]: 3}.

Preview computed fields
4427-0
Evaluate “3”
4425-0

Highlight errors in editor PR

@nyrosmith landed an amazing UI enhancement for distinguishing between pausing due to a breakpoint and pausing on exceptions. When the debugger pauses on an exception the line is now red.

Exceptions
4467-0

Features

@wldcordeiro moved the Source Search UI into a modal. PR This is now consistent with other editors, where cmd+p launches a search modal

Modal
4398-0

@James300 and @bomsy upgraded our jump to location action to support jumping to a line and column. PR While scrolling to the correct column location, might seem like a minor UI detail, this feature was a month in the making and was one of the scarier changes we’ve landed in awhile.

A good way to think about the magnitude of this change is that everything touches location data in some way, breakpoints, call stacks, source maps, search… Getting it right required addressing all of the use cases and fixing almost all of the integration tests. Great work guys!

Jump to Column
4143-0

Testing

Code Health

@ahuth helped us upgrade to flow 53 (PR), which was a huge under taking. Types have been critical for us maintaining code quality while working with so many new comers.

Docs

Infrastructure