process.env not defined with test files.

[lefuncq]

Hi,

I have an e2e test file called ConnectWallet.cy.js containing the following code:

import { WALLETS } from '@/constants';

const elements = {
  ...Object.values(WALLETS).map((wallet) => ({
    [`walletButton${wallet}`]: `[data-testid="connect-wallet-container-wallet-button-${wallet}"]`,
  })),
};

describe('ConnectWallet', () => {
  it('Visitor', () => {
    cy.visit('http://localhost:3000');
  });
});

constants is a file containing constants shared amongst various pages and components of my NextJS App, and some of the values there, are defined using process.env, thus raising a "Referrence Error: process is not defined" error within Cypress's test browser (The following error originated from your test code, not from Cypress.).
I've been searching everywhere but couldn't find a solution that works:

• Setting the env within cypress.config.js will just expose my env variables to Cypress.env which I can't use within constants.js since Cypress.env is, legitimately, undefined when running my next server.
• I've tried loading process.env using on('file:preprocessor', ... but couldn't find how to set up the web pack so that it would "resolve/load" my process.env inside of test files.
  Isn't there any workaround to that issue?