feat: support loading customize environment variables from a .env file

[daychongyang]

No description provided.

[daychongyang]

#213

[yyx990803]

Good job!

[yyx990803]

FYI: inlining the entire env object like this leads to bloated bundle size and also cause the minifier to not be able to drop if (process.env.NODE_ENV !== 'production') blocks, so I am changing it instead replace each key individually.

This will also remove support for usage like process.env['NODE_ENV'] or Object.keys(process.env).

[yyx990803]

See 1be6121

[quantuminformation]

Anyone got a walkthrough doc of how to use this? I am trying to use console.log(import.meta.env) but I only see

vs what I have in .env

I am using svite:

https://github.com/quantuminformation/mentorcv/blob/master/src/index.js#L2

[damianstasik]

@quantuminformation try prefixing your environment variables with VITE_.

[quantuminformation]

wow that was quick, yes that works thx

[stefnotch]

https://github.com/vitejs/vite#modes-and-environment-variables

[daychongyang]

Only variables prefixed with VITE_ are exposed to your code. e.g. VITE_SOME_KEY=123 will be exposed as import.meta.env.VITE_SOME_KEY, but SOME_KEY=123 will not. This is because the .env files may be used by some users for server-side or build scripts and may contain sensitive information that should not be exposed in code shipped to browsers.

// src/node/config.ts     line：455

function loadEnv(mode: string, root: string): Record<string, string> {
  if (mode === 'local') {
    throw new Error(
      `"local" cannot be used as a mode name because it conflicts with ` +
        `the .local postfix for .env files.`
    )
  }

  debug(`env mode: ${mode}`)
  const envFiles = [
    /** mode local file */ `.env.${mode}.local`,
    /** mode file */ `.env.${mode}`,
    /** local file */ `.env.local`,
    /** default file */ `.env`
  ]

  const env: Record<string, string> = {}
  for (const file of envFiles) {
    const path = lookupFile(root, [file], true)
    if (path) {
      const result = dotenv.config({
        debug: !!process.env.DEBUG || undefined,
        path
      })
      if (result.error) {
        throw result.error
      }
      dotenvExpand(result)
      for (const key in result.parsed) {
        // only keys that start with VITE_ are exposed.
        if (key.startsWith(`VITE_`)) {
          env[key] = result.parsed![key]
        }
      }
    }
  }

[quantuminformation]

Nice work guys, i'll promote this build tool on my YouTube channel later today.

[quantuminformation]

btw if any member/contributor wants to come on my podcast to talk about vite, please ping me.

[quantuminformation]

For some reason, I only get one environment var coming through

https://github.com/quantuminformation/mentorcv/blob/master/src/firebaseBackend.js#L12

[daychongyang]

For some reason, I only get one environment var coming through

https://github.com/quantuminformation/mentorcv/blob/master/src/firebaseBackend.js#L12

There seems to be no problem...

[quantuminformation]

Reinstalled nod mods, went away! thx

[quantuminformation]

I tried passing in from command line

➜ mentorcv git:(master) ✗ VITE_EMULATION="true" ndv

however console.log(import.meta.env.VITE_EMULATION) prints undefined