Self-mounting components don't call _mount from ProxyComponent

[ekhaled]

Related to sveltejs/svelte-loader#43
and sveltejs/svelte#1201

when a top-level component calls this._mount() it's calling _mount from the internal instance.. and not from the proxyComponent.
Therefore it does not register itself in the Registry. Therefore, when navigating away and back in sapper, the Registry doesn't have a clue whether the component is mounted and doesn't _rerender the component

How to reproduce

On the sapper-template

1. Go to /about
2. Change something, see it get hot-loaded
3. Go to home
4. Go back to /about
5. Now change something... it won't get hot-loaded

[ekhaled]

Right, misdiagnosis of the root cause.

Although the _mount related stuff above is true, thats not what causes the hot reload to fail.

It fails because when new Component is called in sapper/runtime.js, that Component is not a proxyComponent. It's the original Svelte component.

Still trying to work out the cause, but it seems like somehow webpack returns the "un-heated" component without the proxy wrapper when a chunk is loaded lazily

[ekhaled]

the load() here returns a naked svelte component undecorated by svelte-loader

[ekhaled]

fixed here