e2e tests not reading .local.env file.

Current Behaviour

When I run a react app with @nrwl/web:dev-server, .local.env is loaded, as described here: https://nx.dev/angular/cli/overview#loading-environment-variables

When I run the e2e tests created by the react plugin, the variables are undefined.

Expected Behavior

The e2e version of the front end app should have the variables available.

Steps to Reproduce

Setup an app similar to the react tutorial.

Add a .local.env, with some values that begin with NX_. Console.log those values on app start.

Failure Logs

No failure logs

Environment

➜ yarn nx --version        
yarn run v1.22.4
$ nx --version
9.4.5

➜ node --version                              
v13.14.0

➜ cat /etc/lsb-release                     
DISTRIB_ID=Pop
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Pop!_OS 20.04 LTS"

[cereallarceny]

Update 30/12/20

We’ve now determined that Cypress will load environment variables in the correct order, and NOT overwrite them in subsequent .env files, but ONLY if both environment variable files are placed in the appropriate app folder. In other words, if you have .local.env and .env in the root of your project, you’re going to have problems. If you place those files inside the app that you’re running e2e against, it works as expected.

We would love some clarification on whether this is intentional or not - it still doesn’t seem to be the expected behavior.

[vsavkin]

@Cammisuli @jaysoo we should probably add the same feature to the cypress builder.