Sean Lynch

It seems like the issue might be caused from `azure-function-express`'s [IncomingMessage](https://github.com/yvele/azure-function-express/blob/master/src/IncomingMessage.js) only being an `EventEmitter` and not a stream like express/node's [IncomingMessage](https://nodejs.org/api/http.html#http_class_http_incomingmessage).

I did not, but haven't looked into it in a while. I also haven't tried since the new functions runtime came out. This might be related to the issue as...

Also related - https://github.com/Azure/azure-webjobs-sdk-script/issues/2009 - https://blogs.technet.microsoft.com/livedevopsinjapan/2017/10/07/image-uploading-with-azure-functions-node-js-and-angular-4/ This is currently low priority on my list of things at the moment. This initially came up when I was experimenting with the Functions...

@jonom - If you add the [|local](https://svelte.dev/docs#Transition_events) modifier it fixes/works around this problem. Before: ```svelte I shouldn't be readable (for long)! ``` After: ```svelte I shouldn't be readable (for long)!...

FWIW, I have a gradient component in [LayerChart](https://layerchart.vercel.app/docs/components/LinearGradient) (based on LayerCake) and haven't had this issue myself.

For the derived scale (which in hindsight I should have opened a separate issue not not confuse with the tweened scale use case), I was thinking something like that (but...

As for the tweened scale request, if you notice how Pancake implements the extents, they can be passed as tweened/spring stores. For example, have a look at the [Treemap](https://svelte.dev/repl/2a8acd2328ff4a5398def8b8c8252904?version=3.49.0) example...

Regarding the derived stuff, it might not be worth making them dynamic but instead just expanding the current `x`, `y`, `z`, a `r` scales to also have `x1`, `y1`, `z1`,...

Sounds good. TBH I haven't had time to investigate further since the initial discussion. Once I am, I'll report back.

I might have overlooked the reason, but why not pass `$$restProps` to the underlying component instead of the `attrs` prop container?