Jonas Galvez

Right now it seems to perform about 4.5x better than Node for Vue.js rendering (with the bundled sample app which has zero complexity). I'm waiting until I finish implementing a...

@ErosZy actually the idea is that for everything server-side the Vue application may need, we do it on the Rust side. I'm currently working on fetch/asyncData serialization on the Rust...

@sessionboy I haven't -- but I believe this boilerplate can be used to bootstrap a production-ready app, for sure.

That's already possible. ```svelte ```

> Treat WS as the first-class citizen it deserves to be treated. This should have been done 5 years ago. Especially with the growing popularity of [WAMP](https://wamp-proto.org/)-based apps. +1 on...

@bradisbell you have a valid point -- I just think WebSockets can be considered a _core_ protocol of the web, very much like http2.

@wahengchang for now, import `middleware.js` from a plugin as @alexbonhomme suggested.

As a workaround, you can perform an HTTP request in the `vue-renderer:ssr:context`hook to determine the layout. Something like this (in `nuxt.config.js`): ```js import consola from 'consola' import ky from 'ky-universal'...

Actually, using the same technique, you have access to post-asyncData `data`: ``` 'vue-renderer:ssr:context': (ctx) => { ctx.nuxt.layout = ctx.nuxt.data.layout } ```

Actually, upon further testing, none of this worked for me. What finally worked was having a reusable middleware function in a plugin: ``` import middleware from '../middleware' import myMiddleware from...