Patrick G

>Exactly: `vite-plugin-ssr` aims to be non-invasive and to let you having control over your stack architecture. This plugin is great! And I think the default behavior is very clear and...

> I also definitely prefer the clarity of having separate server and client files. This has been so much nicer to work with than other frameworks that blur the line...

@nathanhammond Something like this: https://www.pzuraq.com/blog/on-signal-relays might allow for a more coarse representation of the reactive graph.

Thanks for letting me know about the issue. I probably should've checked the Solid repo first. Thanks for the feedback! Maybe there is a better way to accomplish my goals?...

> Yep, we don't have a way to bind the JavaScript's [Disposable/AsyncDisposable and to use `using` keyword](https://github.com/tc39/proposal-explicit-resource-management) yet, which has recently reached stage 3 and TypeScript support. I don't think...

This is possible with Solid Start and Nuxt. I think https://nuxt.com/docs/guide/recipes/custom-routing https://docs.solidjs.com/solid-start/building-your-application/routing#additional-route-config (FilesystemRoutes component returns an object which you can add to) https://remix.run/docs/en/main/discussion/routes#manual-route-configuration

I edited the post with some docs links. Sorry

Thats correct. For your use case, I'd suggest just using a client side router (Whose routes can be added to on the server / client) + a backend service that...

[Related Issue](https://github.com/solidjs/solid/issues/1977)

Thanks for the thoughtful response, @matlin, I appreciate you taking the time! That makes sense, and I appreciate the `@triplit/server-core` suggestion, I'll definitely check that out. I understand the concerns,...