There seems to be an issue when you go to /recently-active-users via the client side router, it doesn't render the 404 error, it renders the next unexpected error. It does this because we are not passing the component a statusCode on the client side. Il need to look into how best to provide the statusCode or maybe we can just default to 404.

WIP, this needs more work, don't bother reviewing atm.

Ready for review. I think it can be improved in a few ways, but this is a good starting point.

It looks like there's a whole lot of ad-hoc plumbing in the example that should probably be part of the library. Does every user need to jump through all these hoops and create a dozen different files just to conditionally display a feature page or 404 page?

If so, why?

I'd like to see a minimal example of this in action using about 1/10th as much code. ;)

I'd like to see a minimal example of this in action using about 1/10th as much code. ;)

I agree, that was my goal when I started, but I realized writing this out like a real next app helped me understand the strengths and weaknesses of the current API. I was thinking code like this might make good code for integration tests, we could run integration tests against it with cypress.io. Then we could have simpler example code. What do you think?

Edit: Would make sense to me especially if we create next specific library or provide the next specifics from this library.

Check out how RITEway separately exports a React tool to help React users without requiring all users to install and use React.

As a user, I think I'd prefer it to be colocated with this same library, but perhaps exported separately.

Closing, will go in new smaller example direction after creating new next specific code.