Differentiate between server and client on function level.
Using docker & developing outside docker.
Use-case:
- Imagine you are working with tanstack start and using dynamic server function in loader prop. And inside your server function, you want to fetch some data from the server running on docker.
At first glance, you might think just use the docker service name instead of localhost. But it might not be that simple, because your loader function can also run on client side. Where the docker's internal service name will not work. Also when running tanstack-start in dev mode, api client will require localhost.
Here is my solution, please feel free to provide any other solutions. I'm really looking forwards to see if there are any other great apis/solutions I could use instead of this.
-
-
Use-case:
- Imagine you are working with tanstack start and using dynamic server function in loader prop. And inside your server function, you want to fetch some data from the server running on docker.
At first glance, you might think just use the docker service name instead of localhost. But it might not be that simple, because your loader function can also run on client side. Where the docker's internal service name will not work. Also when running tanstack-start in dev mode, api client will require localhost.
Here is my solution, please feel free to provide any other solutions. I'm really looking forwards to see if there are any other great apis/solutions I could use instead of this.
-
import.meta.env.DEV-
import.meta.env.SSR
