redbar0n

> Hey @redbar0n! Thanks for your feedback! Actually you have a pretty good idea. I could even offer something like 'npm create pax-starter', same way Tamagui or T3 does https://create.t3.gg/...

These Vike (NextJS alternative that's more modular and manual) examples might be a source of inspiration: https://vike.dev/streaming#examples and https://github.com/XiNiHa/vilay - Which is: Vite + Vike + Relay. Was archived, due...

Proxies sounds good. The implementation goes over my head, though. Will probably have more opinions and suggestions as far as the API goes. ```ts user.name.$skip({ if: showName }) ``` looks...

Could this work? ```js query.me.username.value query.me.username.directives ``` I feel like I've seen similar type of API's in JS before, maybe in data or request objects, or maybe on the frontend...

Just a thought: If the underlying implementation is a proxy object, then maybe it is best to use an object as the API instead of chaining, to reduce the impedance...

@vicary ah, I see how it was ambiguous. I was thinking about passing in an object to a function, instead of chaining. But that only works for setting the proxy...

> I am wondering if users would find primitive objects surprising, consider the following example: Yes, I think so. I would for sure. I'm coming back to my suggestion here...

maybe this could serve as some inspiration (grouped allocations/lifetimes): https://www.sophiajt.com/search-for-easier-safe-systems-programming/

You might want to check out https://github.com/Lomray-Software/vite-ssr-boost which integrates Vite with React Router.

See also: https://github.com/oedotme/generouted https://omarelhawary.me/blog/file-based-routing-with-react-router Could maybe be used to import the filesystem dir that Expo Router uses, and if you’d align the conventions on how to interpret those filesystem routes,...