AverageHelper

> How do we fix this ? I guess make PRs along the build chain to update the vulnerable dependencies. Or use `npm audit report --production` to omit dev vulns.

> I'm not sure that it works this way. The originalObj and updatedObj could be fully unrelated @Bessonov I agree with you. This looks safe enough to me though, since...

Popping in to report that @panzelva's gist still works wonders. Plopped it in, and now our project uses modern Joi syntax with full TypeScript inference! (Within reason, obviously, but all...

Agreed. I've missed or nearly missed or thought I'd missed several turns when I couldn't calibrate to the name of the road I'm turning onto. Distance is nice, but I...

I suppose a change like this would need to be tested on both Android and iOS, which might make things difficult.

@suhridkhan I agree. If having that info always visible begins to clutter the UI, we may instead consider hiding that info until about 10mi/15km close.

Oh good, I see Waze has updated since last I used it. Those exit descriptions then were a pain to read on the road. I'd prefer the exit number to...

@jhuggett You *might* be able to work around that: ```svelte // Do your type assertion inside the area! $: presentation = frame.presentation as Basic; ```

[The upstream repo](https://github.com/t3rm1n4l/go-mega/) doesn't seem to have seen updates in a while. It already has two PRs ([#30](https://github.com/t3rm1n4l/go-mega/pull/30) and [#34](https://github.com/t3rm1n4l/go-mega/pull/34)) for adding 2FA. [#34](https://github.com/t3rm1n4l/go-mega/pull/34) seems to pass its CI checks,...

@EinarasGar [go-mega#34](https://github.com/t3rm1n4l/go-mega/pull/34) seems to be the closest relevant PR in the upstream repo. It's awaiting review, possibly from @ncw.