Quentin Gerodel

Like in HAV1, I want to keep the ability to render multiple different pieces of the view accordingly to the route. This is how the `greedy` property works. I am...

Some days ago I was thinking about making a PR. But I was out of the loop from months now about Hav2. I will take the time to read the...

The first warning seem explicitly enough for me. I would move on `VNode | null`. A VNode must not be `undefined` but can be `null`. For the second, I guess...

Untested. I knew that DT use `JSX.Element | null` on some places : https://github.com/DefinitelyTyped/DefinitelyTyped/blob/8ff7e8f29e059f3799c19e0bafb7ac010786ca50/types/react/v15/index.d.ts#L314 I think it is more related to `Element` and not to the `null` as `any` match...

I am currently using ```jsx import { location as router } from "@hyperapp/router" ``` In my build too, since I met some troubles.

Now that the router is Lazy Components first, and Lazy Components will be teared down with the 2.0 release. We will need to work on a new one strongly related...

What is the benefit of the `basepath` property comparing to this simple concatenation ? ```jsx const basepath = "demo" // ... ```

You are responsible to wire the router state to your state, so instead of ```jsx const state = { location: location.state } ``` You are able to use ```jsx const...

Can we close this since #59 is shipped ?

I agree. I needed it in some projects. And the concatenation trick is not really useful.