feat(config): allow user custom .env files directory

[CHOYSEN]

Close #2113

[aleclarson]

Suggested change

	? normalizePath(path.resolve(config.envDir))
	? normalizePath(path.resolve(resolvedRoot, config.envDir))

[aleclarson]

It's probably worth adding a link to the .env guide:

See [here](/guide/env-and-mode#env-files) for more about environment files.

[GavinRay97]

+1, very useful when you have a multi-project workspace and want to keep a top-level .env file with config values for all of the projects.

Would be great to have this merged, thank you =)

[aleclarson]

@GavinRay97 Agreed. Do you want to fork this PR and add the suggested changes so we can merge?

[GavinRay97]

@GavinRay97 Agreed. Do you want to fork this PR and add the suggested changes so we can merge?

Sure np, can do it today after work 👍

[GavinRay97]

Btw, this is how I am working around this now.
This works, but it's ugly:

// vite.config.ts
import reactRefresh from "@vitejs/plugin-react-refresh"
import * as dotenv from "dotenv"
import { defineConfig } from "vite"

const result = dotenv.config({
  debug: true,
  path: require("path").join(__dirname, "../.env"),
})

if (result.error) throw result.error

const defines = {}
for (let key in result.parsed) {
  if (!key.startsWith("VITE_")) continue
  defines["import.meta.env." + key] = JSON.stringify(result.parsed[key])
}

export default defineConfig({
  plugins: [reactRefresh()],
  define: defines,
})

[GavinRay97]

#3407