Fatih Aygün

I'd rather have a common platform *module*. I think of context as the *request* context, i.e. things that change from request to request. HatTip's `ctx.platform` basically holds the platform specific...

> If you want to continue the discussion, please do it elsewhere. I'll close the issue. Sorry for hijacking :) @brillout @mindplay-dk and anyone who wants to continue, we can...

Hi @conartist6, I already have a working resolver I shared in [my comment](https://github.com/import-js/eslint-plugin-import/issues/1810#issuecomment-1188684050). I gladly accept contributions :)

Hi, Thank you for your interest! See the [session example](https://github.com/rakkasjs/rakkasjs/tree/main/examples/session) in the repo, it should give you the direction in which to start. The `entry-hattip` file is for customizing the...

Yes, let's leave it open. It'll serve as a reminder for me to update the docs :)

> My current hunch is a bug somewhere in path handling code in Bun. But I don't know yet When trying to make Rakkas (a Vite-based React metaframework) run on...

I understand the problem and I have a vague idea why it might be happening (NestJS is probably holding some global state that needs to be reset when certain files...

Unfortunately Vite's `ssrLoadModule` that vavite uses under the hood doesn't have HMR support. So `import.meta.hot` will always be `undefined` on the server. The new [Vite runtime](https://github.com/cyco130/vavite/pull/95) does have support but...

A lot of progress on supporting RSC on Vite: https://github.com/cyco130/vite-rsc

This solves pretty much everything: https://unpic.pics/img/