there is not. I generally do not recommend using env vars in the first place.

you can use https://www.npmjs.com/package/dotenv-cli if you really need this

It is not the environment variables in particular... for example api access keys, you don't want to check these in. Something like --config-merge from a file that is ignored by version control.

they shouldn't be in the build period. not by any means.

You‘re probably right to not have an easy mechanism build in that cause people to put secrets where they do not belong. However have some configurations you can overwrite with a local file (not version controlled) often comes in handy. In that regard the api access key was a bad example and your‘re right that it is better to avoid them by any means in the build process because otherwise they most likely leak somehow.

in what context do you need the api key? is it a node targetted build?

I'm not against env vars in general. I'm against using env vars that turn into compile time constants. I think that is the wrong approach the handle them.

I'm not debating whether a .env.local file is useful. it absolutely is. just not to "insert" a build time constant.

e.g. if its a node targetted build you should access them as actual env vars AT RUNTIME. not build time. so just js/process.env.API_KEY

if its a browser targetted build IMHO the html should supply runtime config. and fwiw if its browser, then its public anyway so might as well be in the git repo

It’s currently targeting the browser so it has to be a bound at build time (closure define). The current approach/design (prototype for internal use only) is bad because the api key ends up in the deployed js files.

exactly

so, the way I handle this is putting things like API keys and other config params into the HTML

then they are effectively "environment variables" like they are supposed to be

but all that being said .. if you like env vars and want to stick with them you can via dotenv-cli above

Thank you very much for your feedback. In guess I will use —config-merge for now until there is a proper back-end and client auth.

https://clojureverse.org/t/using-none-code-resources-in-cljs-builds/3745

thanks!