feat: build.target: ['nodeXX'] ignore replace process.env

[caoxiemeihao]

Description

When I use Vite and explicitly specify that the build target is node(Electron App), I hope to bypass the definePlugin

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[netlify]

✅ Deploy Preview for vite-docs-main canceled.

Name	Link
🔨 Latest commit	bcf7967
🔍 Latest deploy log	https://app.netlify.com/sites/vite-docs-main/deploys/62c250635c0e2100091bc1d9

[bluwy]

Perhaps we want to make the fix at

vite/packages/vite/src/node/plugins/define.ts

Line 60 in 1566f61

const replaceProcessEnv = !ssr || config.ssr?.target === 'webworker'

instead.

I don't think we've considered having special treatment for build.target: ['nodeXX'] yet, and so far support for this has been discussed in #7821 only. I'll put this in the team board and let's see how we'd want to support this. I'm assuming this is commonly needed for electron.

[caoxiemeihao]

@bluwy Thanks for your reply, this is indeed an Electron specific scenario. In my project, I had to avoid the vite:define plugin by writing the wizard.

// 🚧 Use ['ENV_NAME'] avoid vite:define plugin
const url = `http://${process.env['VITE_DEV_SERVER_HOST']}:${process.env['VITE_DEV_SERVER_PORT']}`

My project 👉 electron-vite/electron-vite-vue

[benmccann]

Also proposed in #7810. #5577 seems like it might be targeting the same problem as well

[caoxiemeihao]

Yeah! It seems that process.env.XXX always works fine so far.