process.env vs import.meta
process.env is a global variable that is only used by Node at runtime and this can only be used in node and not in the browser. This is the most familiar way to handle environment variables that we do not want to commit into git that could expose some serious sensitive information.
Following is an example of how we use
process.env and usually being used during build time.
_10<script type="module">_10import "./index.mjs?someParams=foo";_10</script>
index.mjs module is able to read the parameters
someParams using the
_10new URL(import.meta.url).searchParams.get("someParams"); // foo
This is something new to me in which it cannot be done when using
For those who prefer to use TypeScript, we can create the relevant types through a global file -
env.d.ts in the root of the project.