envs are not being propagated as expected

[Zidious]

Current behavior

Given that you can supply env via defineConfig via the top level env property, the e2e env property and setupNodeEvents(_, config env property, these appear to not be all propagating to Cypress.env(..)

Desired behavior

Expect all forms of providing envs via defineConfig to be propagated to Cypress.env(..)

Test code to reproduce

Given this example:

module.exports = defineConfig({
  env: { AA: 'AA' },
  e2e: {
    env: { BB: 'BB' },
    setupNodeEvents(_, config) {
      config.env.CC = 'CC'
      return config
    }
  }
})

Placeholder test:

describe('describe', () => {
  it('it', () => {
    cy.visit('https://google.com')
  })
})

Only BB and CC envs are propagated:

Cypress Version

13.13.0

Node version

18.19

Operating System

macOS Sonoma 14.5

Debug Logs

No response

Other

No response

[Zidious]

Hey team! Any update on this at all?

[D0d0d]

Setting your e2e.env as e2e:{env:{...}} simply overwrites top-level env.

As I see, this way we can use top-level env like default, and switch it to another if we need it for another testing type. I couldnt find it in docs, but I believe it is normal case.

If you want to keep your top-level env, but have many fields to add and find dict-view prettier, you can still use something like this:

  e2e: {
    setupNodeEvents(_, config) {
      config.env = Object.assign({}, config.env, { 
        BB: 'Bb' 
      }),

Just my point of view anyway 🐦