James K Nelson

The issue here, I think, is that `withView` doesn't actually match something unless the preceding mounts have matched the complete path up to the final `/`. This is something that...

In Navi, `mount`, `withView`, `route`, etc. are all called "matchers". Currently, other than `mount` and `map`, they will each check to see if there is any unmatched path remaining, and...

Usually this indicates that you've passed something to `mount()` or returned something from `map()` which isn't actually a Navi matcher. I definitely should improve the error messages here. Will aim...

Unfortunately yes, this project is unmaintained, as I no longer have any production projects which use it. For something similar which is still in active development, but completely undocumented, see...

The way to do this is with wildcards on the `mount()`. This lets you direct the mount to fall through to another matcher if it fails to match, which can...

That's a good question. I'm not sure I've got a great answer, but given that `withView` just returns a function, one possibility would be to create a layout, and apply...

@kettanaito, is there any reason that `` won't work for you? https://frontarm.com/navi/en/reference/react-components-hooks/#notfoundboundary

The reason for treating it as an exception up until now is that the way Navi works, a `mount()` near the top of the app doesn't know if a nested...

Not at the moment, unfortunately. It might be worth opening an issue on create react app, as I feel like showing an error screen even on handled errors is an...

Hmm... there's nothing obvious that I can think of. As long as you're calling `register()` in index.js, and you're still using vanilla create-react-app, it should work.