Zacharias Enochsson

@spapas > especially if the changes are minor You can *support* hashes with quite a minor diff, sure. But a router that supports only hash-based routes can get away with...

> But the problems with DRYness and poor maintainability remain. Well the point I was making was mainly that a minimal hash-router implementation and a minimal history-api-router implementation will be...

> @JorgeBucaran In the meantime could you use the solution described by @Swizz? @Swizz solution is basically the same as the workaround I suggested, but for es6 modules rather than...

@lukejacksonn What are your feelings about this? Had to ask since https://github.com/lukejacksonn/hyperapp-fetch will break with the next hyperapp update

@jorgebucaran Nope that's not it. The thing is that the root (of each Page component) *is* unchanging. It's the same no matter which page you are routed to. Even so,...

Aha! Makes perfect sense. Also explains how I was able to work around this behavior by using a common key for the root node of the two pages. Thanks!

I for one am not sure what the question means. @brielov Can you explain more specifically what you want to do? I personally haven’t used SSR, so I can’t answer...

from congwenma/hyperapp-multiselect repo it looks to be for V1

@jorgebucaran In hyperapp-nestable I do it (since a nestable component is an app in itself) and like others have suggested, I use ondestroy

Oh you’re talking about an app unmounting itself! That’s a need I have not yet come across.