.env files in production using adapter-node (pre-built application)

Question

I am trying to deploy a sveltekit app using adapter-node using .env files.

I have a .env file with several values:

V_TEST1=TEST1
PUBLIC_V_TEST2=TEST2

I access them using import { V_TEST1 } from '$env/static/private'; and import { PUBLIC_V_TEST2 } from '$env/static/public';

In development, I have no issues. The values get read and used.

When deploying, there are 2 ways of doing this, one is to build on development side and deploy the necessary files or build server side, sending the whole code to the server and build on the server.

If I build server side, I am able to access the .env I place on the server (different that dev .env) and have no issues. But I do not want to build on the server.

If I build on development side. The environment variables seem to be hard coded into the /build and if I place a .env on the server, the file gets ignored.

On the server I am running using node --env-file=.env build as recommended on sveltkit docs https://svelte.dev/docs/kit/adapter-node#Environment-variables.

So is there a way of accessing the .env files on the server on a pre-build application?

brunnerh · Accepted Answer · 2025-05-12 22:45:44Z

0

You have to switch to the $env/dynamic/* modules if you want to access variables that are loaded when running the application. (Variable access is a bit different via an env object, see docs.)

answered May 12 at 22:45

brunnerh

188k30 gold badges362 silver badges434 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Ben Quan May 12 at 23:49

I managed to make it work using dynamic as you mentioned. But I had to define the variables using pm2 definitions, I could not make it work using the .env file. any thoughts?

brunnerh May 12 at 23:53

Did you run the application using --env-file? With the Node adapter you need to load the variables manually either this way or using a package like dotenv (see this docs section).

Ben Quan May 13 at 0:39

I am running using pm2 arguments: ``` { name: 'myapp', cwd: './myapp', script: 'node build', node_args: '--env-file=.env', instances: 1, autorestart: true, watch: ["./myapp/build/"], env: { PORT: 9100 } }, ```

brunnerh May 13 at 7:06

That looks like it could work if the cwd contains the file. Maybe a pm2 issue of some kind...

Collectives™ on Stack Overflow

.env files in production using adapter-node (pre-built application)

1 Answer 1

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related