[Bug?]: 2.0.0-alpha.2 - process.env not available in server functions

[create-signal]

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Current behavior 😯

Loving the look of V2! I've noticed that when starting a project in dev mode with vite dev, none of the Private Environment Variables (those not prepended with VITE_) are available to Server Functions

.env

MY_SECRET=hello

routes/index.tsx

import { createAsync } from "@solidjs/router";

const myServerFn = async () => {
    "use server";

    if (typeof process.env.MY_SECRET === "undefined") {
        return "MY_SECRET is undefined";
    }

    return "OK";
};

export default function Component() {
    const result = createAsync(myServerFn);
    return (
        <>{result()}</> //Shows "MY_SECRET is undefined"
    );
}

The documentation on Private Environment Variables suggests that this should be OK.

Expected behavior 🤔

process.envshould be available in dev mode

Steps to reproduce 🕹

Steps:

Context 🔦

No response

Your environment 🌎

[create-signal]

Apologies, I found the discussion on Discord and solved by importing dotenv/config at the start of entry-server

Starting the built application with node -r dotenv/config .output/server/index.mjs works also.

Might be worth mentioning in the Migration guide because this behaviour is different from v1

[atilafassina]

Apologies, I found the discussion on Discord and solved by importing dotenv/config at the start of entry-server

Starting the built application with node -r dotenv/config .output/server/index.mjs works also.

Might be worth mentioning in the Migration guide because this behaviour is different from v1

You can load env_vars in compile time with Vite. We describe that in the migration doc config

Other than that, we still want to have better ergonomics and support for runtime env_vars. Work is happening on #2110