server env variables require additonal configuration / packages

[OrJDev]

Currently enviroment variables that are not prefixed with VITE_ will not be loaded,
variables that are prefixed with VITE_ will be exposed to the client (import.meta.env),
what causing it so there is no such thing as server env variable in SolidStart.

this could easily be fixed using dotenv:

import solid from "solid-start/vite";
import dotenv from "dotenv";
import UnoCSS from "unocss/vite";
import { defineConfig } from "vite";
// @ts-expect-error no typing
import vercel from "solid-start-vercel";
  
export default defineConfig(() => {
  dotenv.config();
  return {
    plugins: [
          solid({ ssr: false, adapter: vercel({ edge: false }) }),
          UnoCSS(),
        ],
  };
});

but I think that it should not be handled in our end as SolidStart is a meta framework, and should be loading server variables by default.

[ryansolid]

I agree. I imagine you have an idea of what this should look like. Is it just adding dotenv? Open to following your lead here as I've never really looked at this part in other meta frameworks. I've heard that SvelteKit does well here but that's about it.

[OrJDev]

just make sure to merge and test: examples/bare is where i tested it

#585

Also make sure to mark this as "done" in #576

[apatrida]

Are these build-time or runtime variables? i.e. if you do a production build and have not yet defined VITE_SOMETHING then will VITE_SOMETHING be available on the client if it is only defined before running the build?

SveltKit supports both static (build time) and dynamic (runtime) variables and docker containers, k8s will want to use runtime and not build time since secrets maybe are not baked into the container and are provided later.