Why using JSON.stringify({}) syntax as a workaround?

[ratijas]

About this one: Vitest Browser Mode 2.1.4 regression: ReferenceError: process is not defined #6872. Unfortunately, that 'conversation has been locked and limited to collaborators.' Thus asking here.

The suggested workaround is to add the following to your vitest.config.js/.ts:

export default mergeConfig(
  viteConfig,
  defineConfig({
    define: {
      'process.env': JSON.stringify({}),
    },
  }),
)

Why are we using JSON.stringify({}) here? Looks needlessly complex. Am I missing something? Can't it be simply written as "{}"?

@hi-ogawa

[hi-ogawa]

Can't it be simply written as "{}"?

Yes. define: { someKey: JSON.stringify(someValue) } is sort of a convention about "define" feature in general, so that's why I wrote it so. https://vite.dev/config/shared-options#define

[ratijas]

Thank you for clarification. Marking as answered.