this happens with getClient and setClient because it is a svelte context which is only available at component initialization (construction) and cannot be in an event handler.

Setting it to a lambda will lazily set the default value for that input.

The rationale is that it's actually clearer to eager initialize. You don't need to worry about timing/concurrency that way. Lazy init is inherently more complex than eager init, so there should be a reason to choose lazy over eager rather than the other way around.

setContext must be called synchronously during component initialization. That is, from the root of the <script> tag

It looks like the issue stems from having "svelte" as a dependency instead of a devDependencies in package.json within the sapper project. This causes import 'svelte' to load the rollup excluded npm package's set_current_component instead of from within the sapper generated server.js.

RandomOut: Using a convolutional gradient norm to rescue convolutional filters

Fixup Initialization: Residual Learning Without Normalization

Generalization in Deep Networks: The Role of Distance from Initialization