feat: trpc next middleware

[juliusmarminge]

Closes #38

Sorry, I messed up the previous PR (#74).

[iDarkLightning]

It's nicer to implement auth with the route metadata feature in my opinion since it enabled routes to easily opt in and out of requiring authentication

[juliusmarminge]

Good call. Made a poll on Discord to see which is more used.

Is this worse for performance though? With that approach (using meta) the middleware runs for every request and checking if it should authorize or not, where as with the current (non-meta) the middleware is only run for the endpoints after the middleware? (if it works like that???).

Kind of like Next's old middleware where you had to escape early depending on the url (the url in this case being the meta.hasAuth)?

[iDarkLightning]

Yeah performance wise meta might be slightly worse considering that. As far as I am aware you are correct that the middleware will only run for endpoints inserted after the middleware (unless there's some technicalities I'm missing).

[nexxeln]

Is this ready to be merged now?

[juliusmarminge]

Versioning and changelog left

[nexxeln]

Alright

[nexxeln]

Thanks!