Middleware Explained 

Please never stop making awesome videos. It's super refreshing to hear both of you.

WES BOS. THE MOISTMAKER.

No, no, no authentication in layout while using sveltekit ... It becomes stale upon navigation. Use individual page load functions to check authentication. The Problem with Using Layouts for Auth ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-UbhhJWV3bmI.html Protect SvelteKit Routes with Hooks ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-K1Tya6ovVOI.html

You can actually write middleware outside of the middleware.ts file in Next.js. It’s not as pretty as connect-style middleware, but it is possible. In app router, you simple create a higher-order function that either returns a response or calls the route handler, which is passed in as a parameter.

I think middleware in general is one of the coolest things in web dev

In next.js you can split your middleware into file/ function that export function that take NextMiddleware and return NextMiddleware

Nuxt middleware are really flexible both server and client side

More videos discussing concept like this.

Initialize a database connection in a middleware is definitely not a good idea, that would really increase the time between each fetch-request cycle

On the topic of moist-makers. I hear Americans don't put butter in their sandwiches... that's wild.

Middleware = interceptor