Make a new example app

[maddsua]

Use nextjs this time. Just for funzies

[maddsua]

Found a bug: resetting url case to lowercase prevents some generated nextjs assets from being served; gotta do case resetting in the router further down the pipeline

[maddsua]

Nope, doing that would make some other paths fail; gotta handle that in the fs reader itself

[maddsua]

Also it would be a good idea to put the example app into tar even without any compression to avoid having nextjs artifacts all over the repo. The source itself can be stored in a different repo

[maddsua]

Actually I still don't like the idea of adding a tar parser without the support for gzip, but who uses uncompressed tars? And adding gzip back would break the no-dependency promise. A different approach is required here.

I could make a sorta cron job inside the static reader that would periodically index all the file inside the dist dir and build a map of the paths that are case sensitive (eg are case sensitive).

That job could be triggered on reader init and would run let's say every 60 seconds as new requests come in

[maddsua]

On the other hand, handling the url path case is application's responsibility, not library's.

Case insensitive paths are a double edge sword. Would definitely do that for the router, but for now will keep the path case as it comes from the client

[maddsua]

Even the go http doesn't reset url path case. Welp, done. Now doing the example app itself